What are the best MCP gateways in 2026?
The best MCP gateways in 2026 depend on whether your company already runs its own MCP servers. If it does, Lunar.dev MCPX, Kong, Tyk and Zuplo put a gateway in front of them. If it does not, Mintive (formerly MintMCP), Runlayer, Composio and Elaichi host the catalog for you, while Docker, Cloudflare, Microsoft and Zapier each fit a narrower case. No product wins every situation, so this comparison is sorted by situation, not by rank.
The question usually arrives like a thread on r/mcp puts it. Two hundred people already use ChatGPT, Claude and Cursor. Four systems hold the work: Salesforce, Jira, Notion and Xero. IT has to put one governed layer between those clients and those systems, instead of a drawer full of pasted API keys.
First the jargon. MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps. An endpoint is the address an AI client is pointed at. OAuth is the sign-in standard that lets a person approve access in a browser instead of pasting a key. Single sign-on (SSO) lets people sign in with the company identity provider, and SCIM lets that provider create and remove accounts automatically. An audit log is the append-only history of what happened.
How should enterprise IT teams compare MCP governance platforms?
Enterprise IT teams should compare MCP governance platforms on the same six criteria, read from each vendor's own pages, with gaps left as questions. This comparison follows that method, and it was written by a vendor.
Who wrote it. Elaichi wrote this comparison, and Elaichi is one of the products in it. That is a conflict of interest, so the method is stated here and every claim can be checked.
The six criteria. Every vendor, Elaichi included, is described on the same six:
- Who runs the servers: the gateway vendor, you, or the app's own vendor.
- How clients connect: how many addresses a rollout creates, and how a person signs in.
- The permission model: who a rule can target, and whether it can name a single tool.
- The audit log: what one record holds, and where it can be sent.
- SSO and SCIM: whether the pages state them.
- The pricing model: seats, calls, tasks or a quote.
How vendor facts were checked. Each competitor cell comes from that vendor's own pages, linked in the table and in the section that discusses it, all checked November 2026. Claims about Elaichi come from its product facts, which are checked against the code production runs.
What was not tested. No competitor product was run, no sales call was taken and no quote was requested. Nothing here measures speed, uptime or connector quality. A cell that reads "not stated on the pages linked" means those pages did not say. It does not mean the product lacks it. Rows are in alphabetical order, and there is no overall ranking.
How do the top enterprise MCP management tools compare?
The top enterprise MCP management tools compare most clearly on who runs the servers and how many addresses clients use. Each row below answers the six criteria from the pages in its source column.
| Vendor | Who runs the servers | How clients connect | Permission model | Audit log | SSO and SCIM | Pricing model | Source |
|---|---|---|---|---|---|---|---|
| Cloudflare MCP server portals | Remote HTTP servers you or their vendors run, up to 120 per portal | One portal URL, signed into through Cloudflare Access, then OAuth per server | Allow policies per server; admins pick the tools each portal shows | Access logs each request made with a portal's tools | Sign-in through your identity provider, via Access | Log export with Logpush is Enterprise only; other pricing not stated on the page linked | developers.cloudflare.com, checked November 2026 |
| Composio | Composio's managed toolkits (1,500+ apps listed) plus your own MCP servers; cloud, your VPC or self-hosted | One MCP endpoint per team, SSO-verified | By organization, team, user, agent or toolkit, down to one action | Metadata per call: user, team, tool, action, outcome; no payloads | SAML or OIDC SSO and SCIM 2.0, an Enterprise feature | Metered tool calls: Hobby $0, Pro $29 a month, Enterprise custom | composio.dev, pricing, checked November 2026 |
| Docker MCP Gateway | You run it; catalog servers run as isolated containers | Runs in the background with Docker Desktop's MCP Toolkit, or wherever you start it | Custom catalogs limit which servers are approved | Built-in logging and call tracing | Not stated on the pages linked | Open source; the AI Governance version is invite-only | docs.docker.com, catalog, checked November 2026 |
| Elaichi | Elaichi writes and runs most of its 650+ connectors; native MCP connectors are vendors' own servers; your own remote server on Gold | One address for every organization, https://api.elaichi.ai/mcp; each person signs in with OAuth |
Eight system roles plus custom roles, sharing per resource, and restrictions by role or member, down to one tool | One entry per connected-tool call that reaches execution, naming the person, account and client; Datadog export on Black | SAML or OIDC SSO and SCIM on Gold and Black | Per user: Personal free for one person; Gold lists at $15 and Black at $24 per user per month in USD | elaichi.ai/pricing |
| Kong AI Gateway | Your MCP servers, or tools made from your APIs; data plane in your environment | MCP endpoints provisioned on demand by the AI Gateway | Default and per-tool ACLs for Consumers and Consumer Groups | The plugin logs every allowed or denied attempt | Not stated on the pages linked | The AI MCP Proxy plugin is part of AI Gateway Enterprise | developer.konghq.com, plugin, checked November 2026 |
| Lunar.dev MCPX | Fully self-hosted in your infrastructure, in front of your MCP servers, APIs and models | Not stated on the pages linked | Identity and role-based access, with an admin-vetted catalog | "Immutable logs of all agent activity" | SSO, roles and audit logs listed; SCIM not stated | Licensed per seat: Free up to 50 users, Pro up to 100, Enterprise custom | lunar.dev, pricing, checked November 2026 |
| Merge Agent Handler | Merge's connectors to "hundreds of enterprise systems"; who writes each is not stated | Installed as a remote MCP server with user-made Tool Packs; endpoint pattern not stated | Policy guardrails and DLP on every tool call | Searchable audit trail, on all plans | SCIM-based provisioning through your identity provider | Usage-based credits, free to start; Enterprise custom or seats | merge.dev, checked November 2026 |
| Microsoft Agent 365 BYO MCP (preview) | Remote servers you register, routed through the Agent 365 Tooling Gateway | Copilot Studio, VS Code, Claude Code and GitHub Copilot CLI in preview | Admins approve, reject or block whole servers; tool-level control for these servers is planned | Invocations tracked in Microsoft Defender advanced hunting | Not stated on the page linked | Not stated on the page linked | learn.microsoft.com, checked November 2026 |
| Mintive (formerly MintMCP) | Approved catalog servers plus your own servers hosted on the gateway; US or EU, VPC or self-hosted on request | One URL per role bundle | Permissions set per tool; one switch turns a tool off for every client | Each call logged with user, tool, server and guardrail result; SIEM or OTLP export | SSO via SAML/OIDC; SCIM not stated | Quote only; per-user licensing on active AI agent users | mintive.com, pricing, checked November 2026 |
| Runlayer | Runlayer-built or official vendor connectors, endpoints you add, or servers on Runlayer Deploy; hosted or in your AWS | One Runlayer Plugin URL on your Runlayer host, or a URL per connector | Rules for users, groups, roles or agent accounts, per server or per tool, checked on every call | Actor, on-behalf-of user, credential used and client name (client-reported) | SCIM group sync from your identity provider | Not stated on the pages linked | runlayer.com, docs, checked November 2026 |
| Tyk | Your remote MCP servers, or proxies made from Tyk-managed REST APIs | Not stated on the page linked | Authentication, rate limits, access control and key management at the gateway | Observability at the gateway level | Not stated on the page linked | Remote MCP proxies on all licenses; upstream OAuth and REST-to-MCP need Enterprise Edition | tyk.io, checked November 2026 |
| Zapier MCP | Zapier's own app connections and actions, the ones Zaps use | One shared endpoint; each person's clients reach a server on their own Zapier account | Account-level app and action restrictions, and workspace membership | History tab of tool calls per user; MCP events in the account audit log | Enterprise SAML SSO extends to MCP; SCIM not stated | Your Zapier plan: two tasks per successful tool call | docs.zapier.com, usage, checked November 2026 |
| Zuplo | Remote MCP servers, yours or third-party, or servers made from an OpenAPI file | One gateway with a path per server, such as /mcp/github, and a built-in OAuth server |
Per-tool access by team and by user, decided on every call | Audit trail on the gateway; management audit trail listed as enterprise | SSO with role-based access listed as enterprise | Free tier of 100K requests a month, then volume pricing | zuplo.com, pricing, checked November 2026 |
Two patterns stand out across the rows. Self-hosting is common: Lunar.dev, Runlayer, Composio and Mintive all offer it in some form (checked November 2026). Published prices are rarer: Mintive and Runlayer state none on the pages linked, while Composio, Lunar.dev, Zuplo and Elaichi publish a free tier.
What are the best tools to manage MCP servers across a company?
The best tool to manage MCP servers across a company follows from how the company already works. Find the row that matches, then read that vendor's own pages.
| Situation | Best pick | Why | Source |
|---|---|---|---|
| Engineers already run MCP servers and want the gateway on their own infrastructure | Lunar.dev MCPX | Fully self-hosted, licensed per seat, with a free tier | lunar.dev, checked November 2026 |
| An API platform already carries your traffic | Kong, Tyk or Zuplo, whichever you run | MCP added to a gateway you already operate | Kong, Tyk, Zuplo, checked November 2026 |
| Developers run MCP servers on their own machines | Docker MCP Gateway | Open source, each server in its own container | docs.docker.com, checked November 2026 |
| You already run Cloudflare One | Cloudflare MCP server portals | One portal behind the Access sign-in you already use | developers.cloudflare.com, checked November 2026 |
| Everyone works in Microsoft 365 and Copilot Studio | Microsoft Agent 365, in preview | Registered servers governed from the Microsoft 365 admin center | learn.microsoft.com, checked November 2026 |
| A small team whose automations already live in Zapier | Zapier MCP | No new vendor; app connections and restrictions carry over | docs.zapier.com, checked November 2026 |
| You are building an agent product for your own customers | Composio or Merge Agent Handler | Developer SDKs, per-user connected accounts and usage pricing | composio.dev, merge.dev, checked November 2026 |
| You want a hosted catalog of approved servers, including internal ones written for a laptop | Mintive or Runlayer | Both host your own servers next to the catalog | mintive.com, docs.runlayer.com, checked November 2026 |
| You run no MCP servers, hold many SaaS accounts and support several AI clients | Elaichi | One address for every organization, plus a free plan | elaichi.ai/pricing |
| Three people, one app, one AI client | None needed | Native client connectors hold for a while | When you don't need a gateway |
Servers you already run. Lunar.dev's FAQ says MCPX "is fully self hosted", deployed with Docker or a Helm chart, and its homepage says Boomi has completed its acquisition of Lunar.dev (lunar.dev, checked November 2026). A proxy you run gives you anything your engineers can write, plus the pager. The real cost of self-hosting works through that math, and API gateway MCP against MCP-native compares the two models.
A hosted catalog. Mintive offers "thousands of MCPs they can install in one click, bundled by role", and hosts a company's own servers, including STDIO servers written for a laptop, behind its SSO (mintive.com, checked November 2026). Runlayer's catalog holds connectors "Built and maintained by Runlayer" next to official vendor servers (Runlayer docs, checked November 2026). Where Mintive and Elaichi overlap, the Runlayer alternatives and the Composio breakdown go further.
Developers and agent builders. Composio's homepage says that inside a team's own agent, "Your users connect their own accounts, and Composio runs every call" (composio.dev, checked November 2026). Merge pitches Agent Handler to "Teams building AI agent products" (merge.dev, checked November 2026). Elaichi is built for a company's employees and their AI clients, so a team shipping an agent to its own customers is better served by Composio or Merge.
Which MCP gateway is best for companies using Claude, ChatGPT and Cursor?
For a company on Claude, ChatGPT and Cursor, look for a gateway that creates the fewest addresses and signs each person in as themselves. Most vendors here name all three clients, so the client list rarely decides it.
The address count is what separates them. Composio says "Each team gets its own MCP endpoint" (composio.dev, checked November 2026). Mintive lets a company "Group servers into one endpoint per role", and says people "paste one URL" (mintive.com, checked November 2026). Runlayer's plugin lives at one URL on the customer's Runlayer host, with a separate URL for each connector as well (Runlayer docs, checked November 2026). Zapier MCP clients all use one endpoint, and each person's clients reach a server on their own Zapier account (Zapier docs, checked November 2026). Elaichi uses one address for every organization, https://api.elaichi.ai/mcp, and the person's OAuth grant decides which organization and tools they reach.
Multiply each count by the clients you support and by everyone who joins or leaves. That product is the rollout you will run, and later the offboarding.
One trade-off comes with a single address that serves many apps. A client's own per-tool permission settings then see a few general tools, not each app's tools. In Elaichi those are search_tools, read_tool, execute_tool and run_code, so a Claude or ChatGPT approval setting cannot tell Salesforce from Jira. The gateway's own rules carry that job instead. Each client also keeps its own admin step: which IT admin controls each client gives you covers Claude, ChatGPT and Cursor.
Where does Elaichi fit, and where does it not?
Elaichi fits a company that runs no MCP servers, holds many SaaS accounts and supports several AI clients: Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client. It does not fit a team that wants the gateway inside its own network, or one building an agent product.
What it does. Elaichi is a governed MCP control plane. It writes and runs most of its 650+ connectors. Native MCP connectors are vendors' own servers, which the vendor builds and runs while Elaichi handles sign-in, access and audit. On Gold and Black, an Org Owner or Org Admin can add the company's own remote MCP server under the same rules. Permissions come from roles, sharing decides who may use each connection, toolbox or template, and restrictions decide which connectors and which individual tools a target may reach. In Elaichi, restriction targets are role or user only; the organization default is the absence of a rule, which means allow everything. A rule aimed at a member can only narrow what their role allows, and never replaces or loosens a role rule. The audit trail holds one entry for each connected-tool call that reaches execution (a call refused earlier writes none), and a call from an MCP client is recorded under the person who signed in, with surface mcp and the OAuth client named. The read-only Auditor seat is free.
Its limits.
- Elaichi runs as a hosted service you do not operate. A team that needs the gateway in its own cloud should look at Lunar.dev, Runlayer, Composio or Mintive, each of which offers it in some form (checked November 2026).
- A remote MCP server you add must be reachable over public HTTPS. A STDIO server written to run on a laptop does not qualify.
- A role or restriction change takes about two minutes to take effect. Removing a member, suspending one or revoking a grant is effective on the next call.
- The prompt-injection write gate lives in the Elaichi agent window and does not apply to a raw tool call. What holds on the endpoint is per-operation permissions, scope limits, output redaction and an audit record of each call that reaches execution.
- In Elaichi, export to your own Datadog comes with the Black plan. Other log destinations are not delivered.
- Its regions are EU, US and APAC. An EU or US organization's main data store is pinned to that jurisdiction; APAC placement is best effort, not a residency guarantee.
Pricing is per user. Personal is free for one person, and Gold lists at $15 per user per month in USD, or $10 per user per month billed annually, with SSO and SCIM included. Plans and seat counting gives the price in your currency.
What should you ask every MCP gateway vendor in writing?
Ask every vendor the same eight questions in writing, Elaichi included. A product page says what the vendor chose to publish; a written answer is something you can hold them to in a security review.
- Who writes the connectors, and who fixes one when a third party changes an API?
- Is the endpoint one address for the organization, one per team or role, or one per person?
- Is any URL or token a bearer credential, meaning anyone who holds it can use it, and how long does it live?
- Who can a rule target, and how long does a change take to take effect, measured rather than promised?
- What does one audit record hold: the account the call reached, the client it came through, and argument values or only names?
- What happens to a leaver's access and their connected accounts on their last day?
- Which region holds the data, and is that a guarantee or a placement preference?
- What is the billing unit: seats, tool calls, tasks or a quote?
Each "not stated on the pages linked" cell in the comparison is one of these questions. The billing one has its own worked comparison of per-seat and per-call pricing.
How do you test a shortlist of MCP gateways in a week?
Run the same five steps against every vendor still on the list, and compare recordings rather than decks. Each step tests one of the six criteria.
- Pick one team and one system they use daily, for example support and Zendesk. Ask each vendor who writes that connector and who fixes it when Zendesk changes its API.
- Connect the system, point Claude or ChatGPT at the vendor's endpoint, and have two people sign in as themselves. Count the addresses and tokens the rollout created.
- Turn off one destructive tool for one role, then time how long the change takes to bite. In Elaichi a restriction change takes about two minutes.
- Run five real tasks, one built to fail. Check which account each record names, which client it names, and whether argument values were written.
- Remove one of the two people and check what their client can still do on the next call.
Step five shows how each vendor handles leavers. Browse the connector catalog for the systems that team runs, and see how each function uses governed access. For the definitions behind these shapes, start with what an MCP gateway is.
When do you need none of these?
Six people using AI against two apps, with no auditor asking questions, do not need an MCP gateway. Native client connectors and careful admin settings will hold for a while.
If two engineers run local MCP servers on their own laptops, a company-wide gateway is overhead: the developer holds the key on the machine and shares it with no one. One team building an agent against one internal database needs a server, not a control plane. What these products solve is shared credentials, mixed clients and the question an auditor asks afterward. The case for waiting lists the signals that say you have waited long enough.