Skip to content
Braver New WorldBNW docs

Sharing MCP tools

A capability runs exactly one MCP tool, with its schema pinned. Once one tool of a server is set up (connected, signed in if it uses OAuth, and pinned), its other tools can be shared together:

Terminal window
bnw share tools <CAPABILITY_ID>                               # the server's tools
bnw share tools <CAPABILITY_ID> fetch summarize --access contacts --mode ask
bnw share tools <CAPABILITY_ID> --all --access account --mode auto
  • What each tool gets:
    • its own tool.mcp capability, named and described after the tool, with the input schema the server listed;
    • the same connection and remote-execution consent, with the discovered schema pinned;
    • the same OAuth sign-in: the node keeps one set of tokens for the server, so rotating refresh tokens stay valid;
    • the chosen audience, mode, and per-person limit, and a renewing offer.
  • Consent for remote servers. A remote server receives nothing decrypted until you allow it. Until then, discovery and checks work but calls fail. Allow it on the capability’s Autopilot panel, or with bnw mcp allow-remote <CAPABILITY_ID> (--revoke to stop). Consent covers every capability of this node on that server, and leaves the connection and pinned tools as they are.
  • Limits. Only tools from the server’s most recent discovery can be shared, at most 32 at a time. A tool already shared from the same server is updated, not published again.
  • Tools published without their schema. A tool shared through an earlier descriptor-first setup has no input schema, so requesters can’t see what to send. Sharing it again publishes it once more with its schema, as a new capability under the same name, connection, sign-in, audience, and mode. The old capability’s offer is withdrawn, and it leaves this node’s list (its manifest stays valid, as signed objects do).
  • Readiness first. Tools shared to run on approval or unattended need the server’s consent, their secrets, and any sign-in. These are checked before anything is published, so a refused share leaves nothing behind.
  • In the web client. After discovering the server’s tools on a capability’s setup page, Share more tools from this server does the same. A capability published without its schema shows Republish with schema next to its pinned tool.