MCP protocol support
Which MCP transports and features the gateway supports.
This page lists the MCP transport, endpoints, and sign-in standards the gateway supports. Use it when you connect an agent or MCP server that has no setup guide.
Transport and endpoints
Agents connect to the gateway over the MCP streamable HTTP transport.
The aggregate endpoint is https://<your-gateway-url>/gateway/mcp, and /gateway/mcp/{slug} narrows it to one resource.
A tags query parameter narrows either endpoint to the resources and tools that carry the listed resource tags.
A custom MCP server that you add needs an https server URL.
Authentication
Agents sign in with standard OAuth, and the gateway serves protected-resource metadata as described in RFC 9728.
A client that supports dynamic client registration registers itself on first connect.
The access token must carry the mcp_gateway scope.
The gateway also accepts DPoP-bound tokens (RFC 9449), which stop a stolen token from working without its client key.
An agent that can't run the browser sign-in connects as a custom agent, with an API key or an OAuth credential.
Tool lists and connection details
Policy filters each caller's tool list, so two users at the same URL can see different tools. When an agent connects, the gateway records its client name, version, and MCP protocol version.
For every endpoint, token check, and error response, see Authenticate agents to the MCP gateway.