Agent Gateway
Next Generation Agentic Proxy for AI Agents and MCP servers
What is Agent Gateway?
Agent Gateway is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to next generation agentic proxy for ai agents and mcp servers
Next Generation Agentic Proxy for AI Agents and MCP servers
This server falls under the Cloud Services category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- Next Generation Agentic Proxy for AI Agents and MCP servers
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx agentgatewayConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use Agent Gateway
Agentgateway is an open-source, Linux Foundation-hosted proxy and control plane that unifies traffic routing for LLMs, MCP servers, and AI agents in one gateway layer. It handles authentication (JWT, API keys, OAuth), content filtering, rate limiting, TLS termination, and observability (OpenTelemetry) for any combination of OpenAI, Anthropic, Gemini, Bedrock, and self-hosted model endpoints. Platform teams use it to enforce security policies, route MCP tool calls across multiple upstream servers, and get a single observability point for all agent traffic — either as a standalone binary or as a Kubernetes-native deployment using the Gateway API.
Prerequisites
- Docker or a Linux/macOS/Windows binary environment to run the standalone gateway
- Alternatively, a Kubernetes cluster with Helm for the Kubernetes deployment path
- LLM provider API keys for whichever backends you want to route to (e.g., OpenAI, Anthropic)
- An MCP client or AI agent that will connect through the gateway
- Optional: OpenTelemetry collector for distributed tracing and Prometheus for metrics
Download the agentgateway binary
Download the latest standalone binary for your platform from the GitHub releases page. The binary includes both the control plane and the proxy data plane.
# macOS (arm64)
curl -LO https://github.com/agentgateway/agentgateway/releases/latest/download/agentgateway-darwin-arm64
chmod +x agentgateway-darwin-arm64
mv agentgateway-darwin-arm64 /usr/local/bin/agentgatewayWrite a minimal gateway configuration
Create a YAML config file that defines a listener, an LLM backend, and a route. This example routes traffic to OpenAI's API through the gateway.
# agentgateway.yaml
listeners:
- name: default
protocol: HTTP
port: 8080
backends:
- name: openai
type: llm
provider: openai
auth:
apiKey:
value: "${OPENAI_API_KEY}"
routes:
- name: default
backends:
- openaiStart the gateway
Run agentgateway with your configuration file. The gateway starts listening on port 8080 and proxies LLM and MCP traffic according to your routes.
OPENAI_API_KEY=sk-your-key agentgateway --config agentgateway.yamlConfigure an MCP backend
Add an MCP backend to your config to route tool calls through the gateway. The gateway supports stdio, HTTP, SSE, and Streamable HTTP transports for MCP servers.
# Add to agentgateway.yaml
mcpBackends:
- name: my-mcp-server
transport: http
address: "http://localhost:9000"Point your MCP client at the gateway
Configure your AI client or MCP host to connect to agentgateway's listener instead of directly to the LLM or MCP server. The gateway transparently proxies and enforces all policies.
{
"mcpServers": {
"agentgateway": {
"url": "http://localhost:8080"
}
}
}Deploy on Kubernetes with Helm
For production Kubernetes deployments, use the official Helm chart. The chart installs the gateway controller and configures it to use Kubernetes Gateway API resources.
helm repo add agentgateway https://agentgateway.github.io/agentgateway
helm install agentgateway agentgateway/agentgateway \
--namespace agentgateway --create-namespaceAgent Gateway Examples
Client configuration
MCP client configuration pointing at the agentgateway proxy running locally on port 8080, which then routes to configured backends.
{
"mcpServers": {
"agentgateway": {
"url": "http://localhost:8080"
}
}
}Prompts to try
These prompts work once your AI client connects through agentgateway to both LLM and MCP backends.
- "Route my next request to the Anthropic backend instead of OpenAI"
- "List all available MCP tools registered with the gateway"
- "Check the current rate-limit status for my API key"
- "Show me the last 10 requests that passed through the gateway and their latencies"Troubleshooting Agent Gateway
Gateway returns 401 Unauthorized for LLM requests
Check that the API key is correctly set in your config or environment variable. For OpenAI, verify OPENAI_API_KEY is exported in the same shell session that starts agentgateway. Inspect the gateway logs with the --log-level debug flag for the exact auth failure reason.
MCP tool calls return 'backend not found' errors
Ensure your mcpBackends section in the config file is correctly indented YAML and the address is reachable from the gateway process. Run `curl http://localhost:9000/health` to verify the MCP server is up before starting the gateway.
Gateway binary exits immediately on startup with no output
The config file path may be wrong or the YAML has a syntax error. Run `agentgateway --config agentgateway.yaml --validate` to check for config errors, or add `--log-level debug` to get verbose startup output.
Frequently Asked Questions about Agent Gateway
What is Agent Gateway?
Agent Gateway is a Model Context Protocol (MCP) server that next generation agentic proxy for ai agents and mcp servers It connects AI assistants to external tools and data sources through a standardized interface.
How do I install Agent Gateway?
Follow the installation instructions on the Agent Gateway GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with Agent Gateway?
Agent Gateway works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is Agent Gateway free to use?
Yes, Agent Gateway is open source and available under the Apache-2.0 license. You can use it freely in both personal and commercial projects.
Agent Gateway Alternatives — Similar Cloud Services Servers
Looking for alternatives to Agent Gateway? Here are other popular cloud services servers you can use with Claude, Cursor, and VS Code.
Open WebUI
★ 138.2kUser-friendly AI Interface (Supports Ollama, OpenAI API, ...)
Anything LLM
★ 60.4kThe all-in-one AI productivity accelerator. On device and privacy first with no annoying setup or configuration.
LocalAI
★ 46.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
Nacos
★ 33.0kan easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.
Xiaozhi ESP32
★ 26.7k本项目为xiaozhi-esp32提供后端服务,帮助您快速搭建ESP32设备控制服务器。Backend service for xiaozhi-esp32, helps you quickly build an ESP32 device control server.
Gateway
★ 11.8kA blazing fast AI Gateway with integrated guardrails. Route to 1,600+ LLMs, 50+ AI Guardrails with 1 fast & friendly API.
Browse More Cloud Services MCP Servers
Explore all cloud services servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up Agent Gateway in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use Agent Gateway?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.