claude.ai
A custom connector over OAuth, with the two metadata flags the connector actually checks.
Add the gateway as a custom connector and every chat gets your bindings, with approvals arriving wherever you keep them. Your keys never enter the conversation.
Connect it
- Settings, then Connectors, then add a custom connector.
- Paste https://mcp.sallyport.cloud/mcp.
- Sign in on our consent screen, which names the agent, the workspace and the bindings it will get.
Why the metadata matters
The connector picks client id metadata documents only when the authorization server advertises both `client_id_metadata_document_supported: true` and `"none"` among the token endpoint authentication methods. Miss one of the two and it silently falls back to dynamic registration. Ours advertises both, and there is a conformance test that fails the build if either disappears.
Anthropic reaches our authorization and MCP hostnames from 160.79.104.0/21. A bot-fight rule or a JavaScript challenge on those names breaks the connector while a browser shows a perfectly healthy site.