Troubleshoot MCP tunnels changedconnectors/mcp-tunnels/troubleshooting
Nearest release: v2.1.316, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 30 Oct 2026 22:59 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 30 Oct 2026 23:07 UTC.
Upstream edited
Recorded here
Lines+0added
Lines−4removed
From line
134
where the diff opens
First seen
31 Aug 2026
this site's first read of the page
Recorded edits7to this page, all time
### The Tunnel OAuth configuration toggle is missing
The whole hunk
from line 134, old and new numbered
/
from line 134
134134
135135**Token endpoint** and **Registration endpoint** accept an `https://` URL that is either under `tunnel.anthropic.com` or on the same origin (scheme, host, and port) as the **Authorization endpoint**. Any other URL is rejected, because Claude sends the token exchange and the client credentials to it. Add a route for your authorization server as shown in [Route the authorization server through the tunnel](https://claude.com/docs/connectors/mcp-tunnels/oauth.md#route-the-authorization-server-through-the-tunnel) and enter the resulting tunnel URL. The **Authorization endpoint** field has no such restriction, because browsers load it directly.
136136
137### The Tunnel OAuth configuration toggle is missing
138
139Anthropic enables the option for each organization in the research preview on request. Contact your Anthropic account team.
140
141137## Get help
142138
143139If these steps don't resolve the problem, contact your Anthropic account team with the tunnel domain, the time of a failed request, and the relevant cloudflared and proxy log lines.
No line in this hunk matches that.