MCP
noBGP is driven through the Model Context Protocol. An AI assistant that speaks MCP can list your networks, provision nodes, run commands, move files, publish services and watch events — on machines behind NAT, CGNAT and firewalls that ssh, scp and curl cannot reach.
https://mcp.nobgp.com/mcp?That URL is an MCP endpoint, not a web page — a browser has nothing to show for it. Point an MCP client at it instead; the Public MCP Server page has the setup for each client.
Two servers
There are two, and the difference is who they speak for.
| Public server | Local server | |
|---|---|---|
| Address | https://mcp.nobgp.com/mcp | 127.0.0.1, on any registered node |
| Speaks for | You — every network and organization your account belongs to | That machine — the one network the node belongs to |
| Auth | OAuth 2.0 with PKCE, through the noBGP login page | A bearer token on loopback, registered with the client by nobgp mcp install |
| Turned on by | Having an account | An Owner or Admin granting the node a role with node_grant |
| Can create, destroy, bill and grant | Yes | No |
| Works while the router is unreachable | No | Partly — the node still answers for itself |
Both expose the same tools with the same parameters and the same response shapes. The local one is deliberately the narrower set: a granted node can operate on its own network's machines, but it cannot provision, manage networks or organizations, publish services, or label and grant — which would let a node widen its own reach.
Use the public server for anything account-shaped: your first network, a new node, billing, org and SSO setup, or driving several networks from one conversation. It is also reachable as REST and as a live OpenAPI 3.1 spec, for integrations that are not MCP clients.
Use a node's local server when the assistant should be the machine it runs on — a laptop or a jump box that is itself a node. It survives a router outage for the things the node already knows, and it gives a local Claude the rest of that node's network without an OAuth round trip.
The pages
- Public MCP Server — the endpoint noBGP hosts: connecting a client, authentication and scopes, transport adapters, rate limits and versioning
- Local MCP Server — turning a node's own server on, pointing Claude at it, and troubleshooting it
- MCP Reference — one catalogue for both surfaces: every tool with its parameters, response shape, and which servers expose it
Whichever server you are on, tools/list is the authoritative inventory: it is filtered to what your token — or the node's granted tier — will actually be allowed to do.