One governed proxy for all your agent traffic.
agentgateway
Every call your agents make to tools, LLMs, and other agents, through one place you control.
Your agents talk to a growing list of MCP servers, LLM providers, and other agents, and none of it is secured or observable. agentgateway puts one governed proxy in front of all of it. Let me wire up an MCP server and call a tool through it in about a minute.
A data plane for agent traffic
Open source, Apache 2.0 · one hop for MCP, LLM, and agent-to-agent traffic.
agentgateway is an open source data plane for agent traffic. It puts one governed hop in front of every connection your agents make, to tools over MCP, to LLM providers, and to other agents, and adds security, observability, and governance across all of them. It speaks the agent-native protocols, so it works with any framework.
Install and run it
$ curl -sL https://agentgateway.dev/install | bash
$ agentgateway
# serving UI at http://localhost:15000/uiNo account, no config. It bootstraps a default config and opens a built-in admin UI.
Installing it is one line, and it runs as a single binary. Start it with no config, and it bootstraps a default one and serves a built in admin UI on localhost, port 15000. No account, and nothing runs in the cloud. Everything here is local.
Wire an MCP server
MCP › Servers › Add server · point it at your backend over Streamable HTTP.
Now give it a backend. Start the open source server-everything test server on port 3005. Then in the UI, open MCP, Servers, Add server. Name it server-everything, keep the Streamable HTTP transport, and point it at localhost, port 3005. Save, and the gateway now fronts that server.
Open a session through the gateway
Tool Playground › Initialize · HTTP 200, and every tool the server exposes.
Open the Tool Playground and click Initialize. The gateway opens an MCP session through itself, and lists every tool the server exposes, like echo and a set of get commands. You are already talking to the server through agentgateway, not straight to it.
Call a tool, through the proxy
Pick echo, send a message, Call tool · the
reply came back through the gateway.
Now call one. Pick the echo tool, type a message, and click Call tool. You get an HTTP 200 with your message echoed back, and that whole call flowed through agentgateway. This is the point. Every MCP call now goes through one place, where you can add auth, rate limits, and guardrails.
One front door for your agents
- One governed hop · in front of MCP, LLM, and agent-to-agent traffic.
- Drop-in governance · auth, rate limits, guardrails, and RBAC.
- See everything · OpenTelemetry traces and metrics across every call.
- Runs anywhere · a local binary or a Kubernetes control plane.
curl -sL agentgateway.dev/install | bash · open source, Apache 2.0
That is agentgateway. One governed front door for the tools, models, and agents your agents talk to, with drop-in security, observability, and governance. Run it as a local binary or a Kubernetes control plane. It is open source, and free. Get started at agentgateway dot dev.
