Open Source MCP Gateways in 2026: The Real Options
The open source MCP gateway field is genuinely crowded in 2026: at least nine real, maintained projects let you self-host the layer between your agents and your MCP servers. This is a factual survey of them, licenses and all, checked against each project's own repo or site in late July 2026, plus an honest section on what self-hosting actually costs you. Full disclosure up front: we build Tulimoa, a hosted gateway, so we are the competition to everything below. The facts stand either way.
If "gateway" itself is fuzzy, start with [what an MCP gateway is](/blog/what-is-an-mcp-gateway).
The field at a glance
| Project | License | Shape | Standout |
|---|---|---|---|
| IBM ContextForge | Apache-2.0 | Python, self-host, registry + proxy | Broadest federation: MCP, A2A, REST, gRPC |
| Docker MCP Gateway | MIT | CLI plugin, ships with Docker Desktop | Container isolation per server |
| Obot | Open source + paid enterprise | Control plane, K8s or Docker | Catalog + RBAC + audit in one free bundle |
| MetaMCP | MIT | One Docker, self-host | Namespaces and middleware for curating endpoints |
| Microsoft mcp-gateway | MIT | Kubernetes-native | Session-aware routing, Entra ID, AKS |
| Unla | MIT | Small Go binary | No-code REST to MCP conversion |
| MCPJungle | MPL-2.0 | Self-host, single binary + DB | Tool groups to limit exposure per client |
| ToolHive (Stacklok) | Apache-2.0 | K8s operator + registry | Isolated containers, tool-list optimization |
| agentgateway | Open source (Linux Foundation) | One binary for service, LLM, MCP traffic | Neutral-foundation governance, A2A native |
Two frequent list members intentionally missing: Glama (its gateway is an LLM gateway, not an MCP gateway) and mcp-use (an SDK framework, not a gateway). Both are fine projects that do not belong on this list, whatever other roundups say.
Notes that change decisions
IBM ContextForge is the heavyweight: 4.2k GitHub stars, thousands of commits, and the widest protocol reach of anything surveyed, including wrapping legacy REST APIs and translating gRPC. It assumes real ops capacity (Postgres, Redis, JWT secrets with no insecure defaults). If your org already runs platforms, this is the serious candidate.
Docker MCP Gateway is the easiest yes: MIT, ships inside Docker Desktop's MCP Toolkit, runs every MCP server as an isolated container with restricted privileges, and manages secrets out of env vars. The gateway is free; note that Docker Desktop itself requires paid seats for larger companies. For a local-first dev team already on Docker, this is the shortest path to a governed setup.
Obot is the most complete free governance bundle: catalog, RBAC per user and team, audit logging, self-host or managed, with a $35M-funded company behind the open core and enterprise identity (Okta, Entra) in the paid tier. The usual open-core question applies: the line between free and paid can move.
MetaMCP is the tinkerer's pick: group servers into namespaces, apply middleware to filter or transform requests, expose exactly the endpoint you designed. Unla solves one job well: turning existing REST APIs and MCP servers into managed MCP endpoints from a small Go binary, with the README's own honest warning that it is developing fast and compatibility is not guaranteed. MCPJungle brings tool groups (different clients see different tool subsets), which is an underrated way to cut [context-tax bloat](/blog/the-context-tax) per client. Microsoft's mcp-gateway is the Kubernetes answer with Entra ID and session-aware routing; the natural pick for AKS shops. ToolHive wraps servers in isolated containers with an operator and claims large token savings from tool-list optimization (their number, not ours). agentgateway carries Linux Foundation governance and covers LLM and A2A traffic alongside MCP, which makes it interesting if you want one binary for all three.
What none of them have
One factual observation from checking every project above: none describes a cross-session memory layer. Session affinity, recoverable transport sessions, config persistence yes; an agent that recalls last week's decisions, no. Federation and governance are becoming commodity infrastructure, visible in the sheer length of this list. The layer above it, [a gateway that remembers](/blog/mcp-gateway-with-memory), is where we placed our own bet. Take that as the disclosed bias it is.
Self-host vs hosted, honestly
The self-host pitch is real: your infrastructure, your data path, no vendor between your agents and your tools, and free as in license. The costs are equally real and mostly show up later.
- Ops burden. A gateway is credentials infrastructure. Someone patches it, upgrades it when the MCP spec moves (v2 landed in July 2026), monitors it, and gets paged for it.
- Credential custody. An encrypted vault you operate is only as good as your key management and your discipline. The [gateway security checklist](/blog/mcp-gateway-security) applies to you now, with no vendor to blame.
- The long tail. OAuth flows per upstream, audit storage, dashboards: the parts beyond routing are where self-host time actually goes.
A reasonable rule: self-host when you have platform engineers and a compliance reason to keep everything inside, choose hosted when you want the outcome without the pager. And if you are not sure you need either yet, [that question comes first](/blog/do-you-need-an-mcp-gateway).
Frequently asked questions
What is the best open source MCP gateway?
For enterprise federation depth, IBM ContextForge. For the easiest start on a dev machine, Docker MCP Gateway. For free governance (catalog, RBAC, audit) out of the box, Obot. For curating custom endpoints, MetaMCP. The best one is the one whose shape matches your team, which is why this list leads with licenses and shapes.
Are open source MCP gateways production-ready?
Several are run in production (ContextForge, Docker, Obot, ToolHive all target that explicitly). Production-ready is a property of your operation too: credential storage, upgrades, and monitoring are yours. Some projects, like Unla, say plainly that they move fast; read the README's own warnings.
Is there an open source MCP gateway with a memory layer?
As of our late-July 2026 check of every project above: no. Persistence in these projects means configs and sessions, not agent memory. If cross-session memory is the requirement, you are currently looking at hosted products, ours included.