One MCP to rule them all
One MCP to install — and your agent reaches any of 240+ registered APIs. No per-service setup.
“send an invoice to Acme Corp”
InvoiceNinja
create_invoice
Every service is a bespoke integration
Give an agent real capabilities today and you're writing a bridge per API: auth flow, request schema, error mapping, one bespoke tool definition, repeated for every service it might ever need. It doesn't scale, and most of what you wire up never gets used in a given conversation — it just sits in the context window.
One integration per service. Auth, schema, error handling — all bespoke, all maintained by hand.
One MCP server. Every service is discovered and called the same way, at runtime.
The gateway replaces all of that with one MCP server and a runtime lookup: your agent asks for what it wants to do, the gateway resolves it to a real service from the catalog and calls it. Nothing is wired up ahead of time, and nothing unused sits in context.
0% markup
You pay exactly what the API costs — Stripe's fee is Stripe's fee, OpenAI's rate is OpenAI's rate. We don't take a cut of usage. Subscriptions buy headroom on your monthly cap, not a discount, not a markup. We make money on capacity, not on usage.
Three ideas, one gateway
Plug & play
Install the gateway, run agent-gateway config, add it to your MCP client. No per-service setup.
$ npm install -g agent-gateway-mcp
$ agent-gateway config
$ # add to Claude/Cursor/etc.One card
Pay us, we pay providers. Pay-per-use, billed monthly, 0% markup. Free services stay free.
Invoice — March
OpenAI: $4.32
Twilio: $1.10
Total: $5.42Lazy by default
Your agent only sees the services you've enabled. No context bloat from 240+ unused tools. Drill down only when needed.
> discover()
gmail, stripe, github,
notion, slack (5 enabled)How it works
Four steps. About two minutes the first time. Zero every other day.
Install
One npm install. The gateway is your only MCP server.
npm install -g agent-gateway-mcpConfigure
agent-gateway config opens a local browser page. Sign in, add a card, toggle services on/off.
agent-gateway configWire it up
Add the gateway to your MCP client config (Claude, Cursor, Windsurf, etc.).
{ "mcpServers": { "gateway": { "command": "agent-gateway-mcp" } } }Use
Talk to your agent. It discovers and calls services through the gateway. No further setup.
> "Send an email to Alice about the meeting"240+ registered services
Every one of them reachable from the same gateway, the same way. Enable the ones you need with your own key, or bill the launch set through us.
Run a service?
List it on AgentDNS. Implement /.well-known/agent on your domain, submit, and you're discoverable to every agent using the gateway.