An MCP gateway and an AI gateway solve different problems, and "best MCP gateway" lists often blur them together. What actually matters for Claude specifically is narrower: does the gateway broker MCP servers to Claude Code and Claude Desktop with real auth handling, or is MCP support an afterthought bolted onto something built for routing LLM calls. Ranked below on that basis.
TL;DR
- TrueFoundry ranks first because its MCP Gateway ties directly into Claude Code's and Claude Desktop's managed-settings mechanisms - MDM-enforced allowlisting, per-tool approval gates, and RBAC - not just generic MCP server hosting.
- Docker MCP Gateway is the honest answer for a solo developer or small team wanting containerized MCP servers on their own machine with Claude Desktop or Code - genuinely simpler, but self-hosted and without fleet-wide governance.
- Solo.io's agentgateway, Portkey, and Obot are all real options with real tradeoffs, covered below with where each one falls short specifically for Claude.
1. TrueFoundry
TrueFoundry's MCP Gateway is registration-once, consumption-by-many: a platform team registers an MCP server a single time, and every developer's Claude Code, Claude Desktop, or agent pointed at the gateway uses it without holding its own credentials. What puts it first specifically for Claude: MCP access from Claude Code is routed through the gateway and allowlisted directly inside managed-settings.json, deployed and locked via MDM across a developer fleet, rather than trusting whatever MCP servers individual developers wire up locally. On top of that: RBAC over which servers and tools a team can reach, destructive tools that pause for human approval instead of executing silently, Cedar-based policy for conditions finer than allow/deny, and per-tool metrics (invocation count, latency, error rate) sliced by server and by user.
Key Features:
- Published benchmark - 7 to 12 ms overhead at 200 to 370 RPS
- Gateway continues serving requests on its last-synced config if the control plane goes down
- All rate limiting, load balancing, and auth checks run in memory, no external call in the request path
- MCP gateway with tool-level RBAC, OAuth, and full audit trail, alongside model routing in the same platform
Where it's not the right call: if you're a solo developer running MCP servers locally with no fleet to govern, this is more infrastructure than you need.
2. Docker MCP Gateway (MCP Toolkit)
Docker's MCP Gateway runs each MCP server in its own container, with over 200 pre-built servers available through Docker Desktop and one-click setup for Claude Desktop and Claude Code. Cryptographically signed images and container isolation mean a compromised MCP server doesn't have direct access to your machine. Genuinely the simplest path if you already use Docker Desktop.
Where it's not the right call: self-hosted means you own the maintenance, scaling, and security burden yourself, and there's no fleet-wide RBAC or MDM-enforced policy - it's built for a single developer's machine, not centralizing access across a team.
3. Solo.io agentgateway
Solo.io's agentgateway is Kubernetes-native, contributed to the Linux Foundation in August 2025, with a Rust-based data plane and a CEL-based policy engine for MCP tool RBAC. A strong pick if your platform team already runs Envoy or a Kubernetes-centric gateway layer and wants vendor-neutral governance.
Where it's not the right call for Claude specifically: it's built for platform engineers who own the deployment layer generally, not for the specific problem of getting Claude Code's managed settings and Claude Desktop's preferences pointed at a governed MCP endpoint - there's no documented tie-in to either surface the way TrueFoundry's Claude-specific docs describe.
4. Portkey
Portkey extended its AI gateway into MCP with role-based endpoints that expose only the minimum tools required to each user or team, plus fine-grained auth controls at the org, team, and user level. If you're already running LLM traffic through Portkey, adding MCP governance on the same platform avoids a second tool.
Where it's not the right call: the same caveat as everywhere else Portkey shows up in this series - Palo Alto Networks announced intent to acquire it in April 2026, which is worth weighing before betting Claude's MCP access on its current trajectory.
5. Obot
Obot markets itself as purpose-built for MCP governance - open source, self-hostable on Kubernetes or Docker, with a built-in catalog and multi-role RBAC. Worth naming, with an honest caveat: the ranking claiming Obot is "the best MCP gateway" comes from Obot's own blog post, comparing itself against thirteen competitors and unsurprisingly placing itself first - the same self-serving-source problem worth watching for anywhere in this space, this post included.
Where this ranking doesn't hold
If you're one developer running a couple of MCP servers locally against Claude Desktop, Docker MCP Gateway is might be the right amount of tool, and TrueFoundry's fleet governance is overhead you don't need yet. The ranking above assumes you're solving for an organization with multiple developers, multiple MCP servers, and a real need to answer "who can reach what" - not a single machine.
Which of these are you actually running for Claude specifically, and did the Claude Code/Desktop tie-in factor into the choice, or was that not something you'd considered before picking?
Top comments (1)
The Claude-specific framing is useful. For an enterprise ranking, Iād add a small failure-mode test matrix rather than relying mainly on documented features: does policy fail closed when the control plane is unavailable, how quickly do revocations propagate, is end-user identity preserved all the way to the tool, can an admin pin the exact server/tool schema digest, and do audit events correlate one Claude request to every downstream call? Two gateways can both claim RBAC and approval gates while behaving very differently under stale config, schema drift, or partial outage.