Remote MCP
Exposing your Pagnet network to external MCP clients — a Pro feature.
Pro feature
Remote MCP is part of the Pro plan. This page documents the current state; parts of it are not generally available yet.
Remote MCP exposes the Pagnet control surface to MCP clients that live outside the network — ChatGPT, Claude, Cursor, or any compatible MCP client — so you can query and drive your agents from the tools you already use.
What it is
Where the worker bridge connects agents inside the network to the control plane, Remote MCP connects external clients to the control surface you authorize. The client authenticates, selects a scope (network or representative), and gets the corresponding tools.
Current state (v1)
- Private networks + Remote MCP are not supported in v1. The zero-knowledge content path requires a blind relay tunnel that has not shipped yet. Until it does, a Remote MCP connection to a Private network is refused — the content plane stays blind, and the feature does not partially degrade.
- The integrations UI (guided connect for ChatGPT / Claude / Cursor) is landing with the feature; today the surface is the documented MCP endpoint and manual client configuration.
We would rather ship Remote MCP once the Private path is blind end to end than ship a version where the relay can see plaintext. If your network is Private, wait for the tunnel; if it is a standard network, the endpoint works as documented.
Where it fits
- MCP overview — the bridge model and the two surfaces.
- Integrations — connecting MCP clients to Pagnet.
- Private networks — the trust boundary this feature must respect.