Your platform team already runs Kong in front of the company's APIs, or your network sits on Cloudflare. Then operations asks for Claude to reach Salesforce, Jira, Slack and Google Workspace for three hundred people, most of them outside engineering. Both vendors document MCP features (Kong and Cloudflare, checked October 2026), so the Kong vs Cloudflare MCP gateway question looks like the whole decision. MCP (Model Context Protocol) is the standard way an AI assistant calls tools in other apps.
It is not the whole decision. The harder question is who writes the tools for each SaaS app, who signs each person in to it, and who keeps it working when the app changes. For the general gateway shape, this comparison of API gateways and MCP-native servers covers it. This post is the narrower buyer's version, for Kong and Cloudflare by name.
Kong vs Cloudflare MCP gateway, or a managed connector platform?
Pick Kong or Cloudflare when the tools are your own: APIs you already run, or MCP servers you write. Pick a managed connector platform such as Elaichi when the request is a list of SaaS apps and the people asking are not engineers.
The split follows from what each product starts with (vendor docs checked October 2026). Kong starts from your APIs and asks you to describe them as tools. Cloudflare starts from MCP servers, either ones you deploy on Workers or remote ones you add to a portal. Elaichi starts from the apps. It serves 650+ connectors, most of which it authors, through one organization-wide endpoint, https://api.elaichi.ai/mcp. An endpoint here is the one address every client points at.
Between the two, Kong fits when the tools are APIs you already run behind it, and Cloudflare fits when engineers build servers on Workers or put remote servers behind a portal. Cloudflare's gateway-style MCP product is MCP server portals.
None of these is better in general. Each fits a different upstream, and the sections below show where each one's work lands.
What does Kong AI Gateway do with MCP?
Kong AI Gateway turns APIs into MCP tools and proxies MCP traffic, inside a gateway your team operates. Kong's AI Gateway documentation (checked October 2026) says it "is managed through Konnect", with data plane nodes running "in your environment". It lists the job as "Turn existing APIs into tools an AI agent can discover and call over Model Context Protocol".
The building block is the AI MCP Server entity (checked October 2026). Kong's page says "Each tool needs at minimum a description and an HTTP method". Kong's API-to-tools tutorial has the reader write each tool's name, description, method and path, against the Swagger Petstore sample. The AI MCP Proxy plugin can also pass MCP requests through to an upstream MCP server. Kong marks that plugin "only available as part of our AI Gateway Enterprise offering".
Kong's access control is fine-grained. The proxy plugin evaluates allow and deny lists against Kong Consumers and Consumer Groups, at a default level and per tool. The AI MCP OAuth2 plugin (checked October 2026) validates tokens by introspection or JWKS. It also notes that "Access tokens are not forwarded to upstream services by default".
What does Cloudflare offer for MCP servers?
Cloudflare documents two MCP products that matter here: a place to run MCP servers you write, and a portal that puts several remote MCP servers behind one address. Cloudflare's remote MCP server guide (checked October 2026) deploys a server to a workers.dev subdomain. In its authentication example, "your users are redirected to GitHub to authenticate".
The second product is MCP server portals, part of Cloudflare Access in Cloudflare One. Cloudflare's MCP server portals page (checked November 2026) says a portal "centralizes multiple Model Context Protocol (MCP) servers onto a single HTTP endpoint". Users sign in through Access and "are prompted to authenticate separately to each server that requires OAuth". Admins choose and rename tools per portal, and Access logs each tool request.
The same page sets the limits. "Only remote HTTP MCP servers are supported", and "Each portal supports up to 120 MCP servers." An admin adds each server by its URL. So the portal works best when every app already publishes a remote MCP server, or when your team builds one on Workers.
Are Cloudflare's MCP server portals where enterprise MCP governance is heading?
Portals are one clear shape of central MCP governance, not the only one. Cloudflare's portal docs (checked November 2026) put several remote MCP servers behind one address, sign people in through Access, let admins choose the tools and log each tool request. An admin adds each server by its URL, and the tools come from those servers.
A thread on r/ClaudeAI asks whether this portal model is where enterprise MCP governance is going. Cloudflare's MCP server portals page (checked November 2026) shows where its control sits. A server link "will only appear in the portal for users who match an Allow policy". The same page cautions that "Blocked users can still connect to the server (and bypass your Access policies) by using its direct URL", unless Access is that server's OAuth provider. Portal traffic can also go through Cloudflare Gateway "for richer HTTP logging and data loss prevention (DLP) scanning".
So the useful question is which layer holds the rules. A portal enforces them in front of servers you add. Elaichi enforces them inside the connectors it serves: one role per member, restrictions per role or member, and an audit row for each call that reaches execution. If every app you need already publishes a remote MCP server, and Access is already your sign-in, a portal may be all you need.
Who writes the Salesforce, Jira and Slack tools on each path?
On Kong and Cloudflare, your side builds or adds the tools. On Elaichi, Elaichi writes and maintains most of the connectors, the app vendor runs the rest, and your side connects accounts.
With Kong AI Gateway, someone describes each tool: name, description, method and path, per endpoint, per app. When Salesforce changes an endpoint, that description is yours to fix. With Cloudflare, a Workers server is code your engineers write and deploy. A portal can instead front an app's own remote MCP server, such as Atlassian's for Jira or Slack's (both checked October 2026). Each one still needs adding, an OAuth setup and a check on its tool names.
Elaichi starts from the other end. It serves 650+ connectors and authors most of them, including Salesforce, Jira and Slack, and serves them from its own infrastructure. Google Workspace arrives as several connectors, such as Gmail, Drive and Calendar. A missing app can be a custom connector, written from JSON config or forked from a public one. Why first-party authorship matters covers the repair path in detail.
How does each path sign a person in to the SaaS app?
In Elaichi, each person signs in to each app with their own account, and a separate service holds and refreshes those tokens. On Kong and Cloudflare, the per-person path to the app is something you configure.
Kong's AI MCP Server page says that, by default, "AI Gateway proxies these requests without adding credentials", and config.upstream.auth sets what Kong adds. Kong's OAuth2 plugin can swap the client's token for another one before forwarding (both checked October 2026). Ask Kong which token endpoint would issue a per-person Salesforce token, and who registers that app. On Workers, Cloudflare's authorization docs (checked October 2026) say "the MCP Server (your Worker) generates and issues its own token to the MCP client" when a third-party provider signs the user in. Cloudflare's portal supports per-user OAuth to each upstream server through its "Require user auth" setting. With it disabled, users reach the server through its admin credential. Ask Cloudflare which account each tool call reaches in each mode.
In Elaichi, a Member can connect any catalog app with their own account unless a restriction stops it. Credentials live in a separate credential service, encrypted at rest with AES-256-GCM, and that service owns refresh. A failed refresh marks the connection needs_reauth, so the failure shows. An OAuth connector connects through a default OAuth app that every organization inherits unless it brings its own. Where none exists, the catalog marks the connector, and an admin with connector-management permission stores the organization's own client ID and secret first.
How do Kong, Cloudflare and Elaichi compare side by side?
Kong and Cloudflare are for the reader who already runs the upstream: APIs behind a gateway your team operates, or MCP servers your engineers deploy and front. Elaichi is for the reader who wants a catalog of SaaS apps where Elaichi authors and runs most of the connectors itself.
The vendor columns were re-read on developer.konghq.com in October 2026 and on Cloudflare's portal page in November 2026. Kong's AI Gateway docs still describe AI Gateway as a connectivity and governance layer that puts LLM, MCP and agent-to-agent traffic under one control plane, managed through Konnect with data planes in your own environment (checked October 2026). Cloudflare's portal docs still describe a portal as several remote MCP servers behind one HTTP endpoint, behind Access (checked November 2026).
On the managed side the pieces are concrete. Claude, ChatGPT, Cursor and Microsoft Copilot all sign in at one address, https://api.elaichi.ai/mcp, the same string for every organization. Each person approves their own OAuth grant, so every call acts as that person in the organization they picked. A restriction targets a role or one member, never a team and never the whole organization. Every call that reaches execution writes an audit row naming the person, the connector, the connection and the MCP client.
| Kong AI Gateway (checked October 2026) | Cloudflare Workers and MCP server portals (checked November 2026) | Elaichi, a managed connector platform | |
|---|---|---|---|
| Where tools come from | Tool definitions you write over your APIs; the proxy plugin can also front an upstream MCP server | MCP servers you write on Workers, or remote servers an admin adds by URL | 650+ connectors, most authored by Elaichi; native MCP connectors are vendors' own servers |
| Who runs the connectors | Your team. Kong's docs say each tool needs at minimum a description and an HTTP method | Your team, or the vendor whose remote server you add to a portal | Elaichi runs most of them on its own infrastructure; the vendor runs a native MCP connector |
| Where it runs | Data planes in your environment, managed through Konnect | Workers, and portals behind Cloudflare Access | Elaichi's infrastructure. The organization's data store sits in the region chosen at creation |
| Address for clients | Route paths you configure | One portal URL per portal | One URL, https://api.elaichi.ai/mcp, for every organization |
| Sign-in model | Kong proxies without adding credentials by default; config.upstream.auth sets what it adds, and the OAuth2 plugin can exchange the token |
Access signs the person in, then each OAuth server is authenticated separately. With "Require user auth" off, the portal uses the admin credential | Each person approves their own OAuth grant and connects each app with their own account |
| Documented limits | Ask Kong. The MCP Proxy and OAuth2 plugins are AI Gateway Enterprise only | Only remote HTTP MCP servers are supported, and each portal supports up to 120 MCP servers | 25 organization-owned remote MCP connectors, 500 tools per connection, 120 MCP requests per 60 seconds per grant |
| Access rules | Allow and deny lists per tool, on Consumers and Consumer Groups | Access policies per portal and per server link, plus admin tool selection | One role per member, restrictions per role or member, frozen parameters on toolbox entries |
| What the audit log records | The proxy plugin writes every access attempt, allowed or denied, to its audit log | Access logs the individual requests made using the portal's tools; Logpush export is Enterprise only | one entry for each connected-tool call that reaches execution (a call refused earlier writes none), naming the account reached, plus the MCP client |
| Who maintains what | Your team maintains each tool definition and each upstream change | Your team maintains Workers code and portal membership; vendors maintain their own servers | Elaichi maintains most connectors; your admins maintain roles, restrictions and shares |
Which shape fits your company? A decision checklist
Run these four checks in order and stop at the first that decides it. Each one maps a fact about your company to one of the three shapes above.
How many apps, and whose? One or two internal APIs you already run behind Kong: Kong AI Gateway. A handful of apps that each publish their own remote MCP server, and nothing else: a Cloudflare portal, within its documented limit of 120 MCP servers per portal (checked November 2026). Dozens of third-party SaaS apps, most of which publish nothing: a managed connector platform, because somebody has to author each connector.
Do you have platform engineering capacity? Kong's tool definitions and Cloudflare's Workers servers are code your team writes and keeps working when an API changes. If no one owns that queue after the pilot, the connectors rot. A managed platform moves that maintenance to the vendor for the connectors it authors, and leaves you roles, restrictions and shares.
Do you need per-person OAuth to each app? On Cloudflare, a portal supports per-user OAuth through its "Require user auth" setting, and with it off the portal uses the admin credential (checked November 2026). Whether Kong can issue a per-person token for a SaaS app such as Salesforce is a question to put to Kong, because its own OAuth2 plugin page does not document that outcome (checked October 2026). In Elaichi, each person approves their own grant and connects each app with their own account, so every call acts as that person.
What does compliance need? If the answer is per-person attribution on every call, in one place, ask each vendor what its log records: Kong's plugin writes each access attempt, Cloudflare Access logs each tool request, Elaichi writes one entry for each connected-tool call that reaches execution (a call refused earlier writes none). If the answer is a chosen data region, note that Elaichi's EU and US organizations keep the data store and org-scoped execution in that jurisdiction, while APAC is best-effort placement, not a residency guarantee. If the answer is a certification, read the Trust Center rather than any claim here.
Two honest outcomes. If your whole list is internal APIs, you do not need a connector catalog. If your whole list is apps that already ship remote MCP servers, and Access is your sign-in already, a portal is enough.
Can you connect a whole tech stack to AI assistants without building MCP servers?
Yes, if the platform already wrote the connectors. That is the case a managed connector platform is built for, and the case where a gateway leaves the most work on your side.
In Elaichi, an admin adds https://api.elaichi.ai/mcp once, each member signs in with their own OAuth grant, and members connect their apps from the catalog. On the other paths, you describe each tool in Kong, or add each server to a Cloudflare portal by its URL. The endpoint, sign-in and audit details are covered in the gateway comparison.
Two Elaichi points matter next to Kong and Cloudflare. Frozen parameters lock an argument, such as a Slack channel, so the model cannot change it. The model can still see a short frozen value in the tool description. One condition: a freeze binds only calls made through its toolbox entry, so share the toolbox with the people it governs, not the connection itself. And the organization picks a region, EU, US or APAC, when it is created. For EU and US, the organization's data store and the execution of its org-scoped requests and tool calls stay in that jurisdiction. APAC uses best-effort placement and is not a residency guarantee.
How do you move from one shape to another?
Move one app at a time, and keep the old path running until the new one carries real traffic. Three steps, with nothing to install beyond what each vendor already documents.
Inventory what you run now. Write down each MCP server in use, who added it, which app it reaches and which account its calls land on. Cloudflare's portal lists the servers an admin added, and Kong's entities list the tools you defined. Local servers on people's machines are the hard part: none of the client admin pages read in October 2026 documents an inventory of them, so you ask, or you read the config files on each device.
Pilot one app with one team. Pick an app with low blast radius and a clear owner, connect it on the new path for five or six people, and leave the old path in place. In Elaichi that means one connector, one toolbox and one restriction rule on the pilot role, so you see refusals before the whole company does. Watch the audit log rather than asking people whether it worked.
Cut over, then retire. When the pilot team stops using the old path, move the next app, and only then remove the old server or tool definition. Keep the record of what moved and when, because a half-migrated estate with two sources of truth is worse than either shape on its own. Assign each tool to exactly one layer, so a policy change is made once.
When is Kong or Cloudflare the better choice?
Kong is the better choice when the tools are your own APIs and Kong already fronts them. Cloudflare is the better choice when your engineers are building MCP servers and want them on Workers, or want one portal over remote servers they already trust.
With Kong, an internal order API becomes tools through an AI MCP Server entity, with Consumer allow and deny lists your team already knows how to review. With Cloudflare, an engineering team writing custom servers gets Workers hosting, OAuth options and Access in one account (checked October 2026). If your apps all publish remote MCP servers, a portal over them is a reasonable shape too.
Elaichi does not fit those cases well. It is not built to front a fleet of servers you run, and it governs an app's own MCP server only when that server is in its catalog or added as your own remote MCP connector. The cost of running your own servers is the honest test for the build path.
How does Elaichi run alongside Kong or Cloudflare?
Split by who owns the upstream: internal APIs stay behind Kong, servers your engineers write stay on Cloudflare, SaaS accounts go through Elaichi. Kong keeps request policy over APIs you deploy, and Cloudflare keeps hosting and Access for servers you build, so neither has to front Salesforce. The side-by-side split is covered in the gateway comparison.
To compare more shapes, read what an MCP gateway is, the shortlist of MCP gateways, or the Docker MCP Gateway comparison. To check your own stack, browse the connector catalog and the team rollouts.