Connect Claude web and Managed Agents
Claude on the web and Anthropic Managed Agents reach your tunnel over Streamable HTTP at its public URL, the same as every other client. You add it as a remote MCP server in the workspace and paste the tunnel URL:
https://notes--acme.mcppipe.dev/mcpWhere exactly that field lives in the interface is Anthropic’s to document and changes with their UI, so follow their instructions for adding a remote MCP server. Everything below is the mcppipe side, which is what actually differs from a desktop client.
The important difference: the request does not come from your machine
Section titled “The important difference: the request does not come from your machine”Claude Desktop, Cursor, VS Code and the rest run locally — they call your tunnel from your network. Claude on the web and Managed Agents do not. The request originates from Anthropic’s infrastructure.
That inverts how you lock the tunnel down:
- With a desktop client, the IP allowlist entry is your own egress IP.
- With Claude on the web or a Managed Agent, your own IP is irrelevant. The entry has to be Anthropic’s published egress range — which is what the Anthropic one-click preset is for.
Getting this backwards is the usual cause of a
403 ip_forbidden that appears only when you move
from the desktop app to the web.
If you want both to work, use the Multi-LLM preset (Anthropic + OpenAI) and add your own egress IP alongside it.
Authentication
Section titled “Authentication”A cloud agent is exactly the case where leaving a tunnel open to the whole internet is least comfortable, and where an IP allowlist alone is a coarse control — the range is shared by every customer of that vendor.
Switch the tunnel’s auth mode to OAuth so callers must present a token. For an agent that runs unattended, mint a Service Token rather than relying on a browser consent flow. See Authentication: OAuth & Service Tokens.
Reliability matters more here
Section titled “Reliability matters more here”A cloud agent’s session can outlive your laptop’s network. mcppipe resumes a dropped CLI session and replays buffered frames, within bounds — see Reliability: reconnect & sessions for the exact limits, and consider running the CLI somewhere that stays up if the agent is scheduled rather than interactive.
See also
Section titled “See also”- Client compatibility — the full matrix
- IP allowlist & access control
- Claude Desktop — the local case, with the opposite allowlist advice