Add a custom MCP server
Connect a remote server using its public HTTPS MCP endpoint.
Check compatibility
The current path requires Streamable HTTP and the supported provider OAuth flow. The endpoint must be a public HTTPS destination accepted by the connection checks.
Register the server
In the Admin workspace, open Connections.
- Open Admin → Connections → All providers and select Custom MCP.
- Enter the exact public HTTPS endpoint without credentials, query strings or fragments. Choose User signs in, OAuth, and Advanced → Streamable HTTP, then save setup.
- Complete provider OAuth, discover tools, and review permissions and resources.
- Complete the read-only test and resolve any validator or provider-acceptance blockers.
- Review the current activation and billing preview before enabling.
Troubleshooting
The reviewed endpoint includes query parameters
Keep the draft disabled and ask for reviewed runtime support. Do not remove parameters: they can change the catalog or permission profile.
My server requires an API key in custom headers
The current MCP path does not forward custom headers, even if saved in a draft. Confirm a supported OAuth authentication path with the server owner before retrying.
Frequently asked questions
Can I use a private or on-premise server?
Private reachability requires a supported mechanism or approved customer-side bridge. Registering a private URL does not make the server reachable from the hosted gateway.