For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.
Servers
Connect agentgateway proxies to MCP tool servers via various transports
Connect agentgateway to an MCP tool server.
Why put agentgateway in front of an MCP server?
| Without agentgateway | With agentgateway |
|---|---|
| Direct client-to-server connections | Centralized gateway for all MCP traffic |
| No authentication layer | External authentication (OAuth2, Tailscale, etc.) |
| No observability | Full OpenTelemetry tracing and metrics |
| No rate limiting | Per-client and per-tool rate limits |
| No access control | Fine-grained authorization policies |
| Clients must handle each transport | Unified endpoint for all transports |
Stdio
Run a local MCP server as a subprocess and expose it through agentgateway over stdio.
Streamable HTTP
Connect to MCP servers via streamable HTTP with automatic session management
Virtual MCP
Federate multiple MCP servers into a unified virtual MCP backend
OpenAPI
Expose OpenAPI endpoints as MCP tools in the agentgateway UI playground
Was this page helpful?
