Open-source MCP gateway

The open-source MCP gateway for every system your AI agents need to reach

Give Claude, ChatGPT, Copilot and Cursor one secure endpoint instead of a separate MCP server per system. AnythingMCP turns your REST, SOAP, GraphQL and SQL systems into MCP tools without code, and decides per user which tools each agent can call. Run it with Docker on your own servers or on AnythingMCP Cloud in Frankfurt.

Start the 7-day free trial Self-host from GitHub

Open source (AGPL-3.0) · self-hostable with Docker · EU cloud in Frankfurt · AES-256-GCM encrypted credentials

What is an MCP gateway?

An MCP gateway is a single Model Context Protocol (MCP) endpoint that sits between AI agents and the tools, APIs and MCP servers they use. Instead of connecting every agent to every system separately, the agent connects once to the gateway, which handles authentication, decides which tools each user may call, records every call in an audit log and routes each request to the right backend. It gives an organisation one place to control what AI agents can see and do.

MCP (Model Context Protocol) is the open standard that Claude, ChatGPT, Copilot, Cursor and other AI clients use to call external tools.

Why teams put a gateway in front of their AI tools

Connecting one assistant to one system is easy. The problems start at the third system and the tenth user.

One MCP server per system doesn't scale

Every system gets its own server to deploy, patch, monitor and register in every AI client. With a gateway, clients connect to one URL and you add systems behind it.

Credentials end up everywhere

API keys and database passwords get copied into config files on laptops and into every server. A gateway keeps them in one encrypted store, and the AI client never sees them.

Nobody can say what the agent did

Without a central log there is no answer to “which records did the assistant change last week?”. A gateway records every tool call: who made it, with what input, and what came back.

Everyone gets the same tools

A plain MCP server gives every user every tool it has. A gateway maps tools to roles, so sales can read orders while only finance can issue a credit note.

What AnythingMCP's gateway does

AnythingMCP is a gateway that also builds the tools behind it. Point it at the systems you already run and it serves them to AI clients through one governed endpoint.

Tools from the APIs you already have

Import an OpenAPI or Swagger spec, a Postman collection, a WSDL, a GraphQL endpoint or a database connection and get MCP tools without writing code. Supported databases: PostgreSQL, MySQL, MariaDB, MSSQL, Oracle, MongoDB and SQLite.

SOAP and on-prem databases

Existing MCP servers behind the same endpoint

Already running MCP servers? Connect them as MCP connectors and expose only the tools you choose, under the same access rules and the same audit log.

Ready-made connectors

721 ready-made connectors for ERP, accounting, CRM, e-commerce, logistics and more, installed in a few clicks.

Browse the marketplace

OAuth 2.0 and per-user MCP API keys

AI clients sign in with OAuth 2.0, so adding the gateway to Claude or ChatGPT is a login, not a pasted secret. For scripts and other clients, each user can create their own MCP API keys.

Role-based tool whitelists

Decide per role which connectors and tools are visible. Publish a server that can only read, which is how most teams should start with an ERP. Tools carry read-only and destructive hints, so a client can tell reading an invoice from issuing a credit note.

An audit log of every call

Each tool call is recorded with the user, input, output, duration and status. When you self-host, the log lives in your own PostgreSQL database.

Encrypted credentials

API keys, passwords and OAuth refresh tokens are stored AES-256-GCM encrypted. The AI model never sees them.

Who builds AnythingMCP

SSO and SCIM when you self-host

Sign in with Entra ID, Google, Okta, Auth0 or any OIDC provider, and provision users with SCIM. Roles follow your directory groups; disable someone in the directory and their access and MCP API keys stop working. Comes with the self-hosted Enterprise edition, which you can try for 30 days on your own instance; not available on AnythingMCP Cloud.

A knowledge graph of how your systems relate

The gateway maps the entities your connectors share, such as a customer ID in the CRM and in the ERP, and serves that map to the agent as a tool, so it chains calls across systems correctly.

Per-tool rate limits

Give each role's access to a tool a limit per minute and per hour, so a looping agent cannot flood your ERP with calls. Set it per role under Settings → Roles, or through the API and the CLI.

Code Mode

The agent writes one short program that calls several tools in an isolated sandbox with no network and no secrets, so a five-step lookup becomes one call. Each inner call is checked and logged like a direct one. Code tools that write need Enterprise.

How Code Mode works

Skills, memory and File Search

AI skills hold the procedures your agents follow, in every edition. Company memory, saved in one AI client and found again in another, comes with Enterprise. File Search indexes SFTP, WebDAV, S3 or NAS folders: included on Cloud, Enterprise when you self-host.

How MCP gateways differ

“MCP gateway” covers products that solve different problems. Most fall into one of three groups, and the right one depends on what you already have.

Proxy and security gateways

They sit in front of MCP servers you already run and add central sign-in, policies, logging and routing. A good fit when every system you care about already has an MCP server.

API and AI gateways with MCP support

Existing API management or AI traffic platforms that extend their policies to MCP traffic. A good fit when your organisation has already standardised on one of them.

Gateways that also build the tools

They create the MCP tools from your APIs, SOAP services and databases, then govern them in the same place. This is where AnythingMCP sits; through its MCP bridge it can also take in existing MCP servers.

MCP gateways compared

What AnythingMCP, Kong AI Gateway, Docker MCP Gateway, Composio and Zapier MCP each document about the points that decide a gateway choice.

Feature	AnythingMCP	Kong AI Gateway	Docker MCP Gateway	Composio	Zapier MCP
Open source	Yes, AGPL-3.0	Gateway core Apache-2.0; MCP proxy plugin in the Enterprise offering	Yes, MIT	SDK under MIT; the platform is not open source	No open-source licence stated
Self-hosted	Yes, with Docker	Yes, self-managed or hybrid	Yes, with Docker	Enterprise only (Helm or VPC)	No
Hosted service	AnythingMCP Cloud in Frankfurt (EU)	Konnect, with an EU region	Not stated	Composio Cloud, region not stated	AWS US-East-1 (US)
MCP tools from REST and OpenAPI without code	Yes, also GraphQL and OData	Yes, from REST routes or an OpenAPI spec	Not stated; runs existing MCP servers	Custom tools are written in SDK code	Not stated
SOAP services and SQL databases	Yes: WSDL, PostgreSQL, MySQL, MSSQL, Oracle, MongoDB and more	Not stated	Not stated	Not stated	Not stated
Existing MCP servers behind one endpoint	Yes, MCP bridge	Yes, proxy and aggregation	Yes	Experimental, remote servers only	Not stated
Ready-made integrations	721 connectors	Not stated	300+ verified servers	1,500+ toolkits	9,000+ apps
Tool access per role or user	Per role and per tool, every edition	Per-tool ACLs by consumer group	Tool allowlists per profile	Allowed tools per MCP server	App and action controls (Enterprise)
Rate limits per tool	Yes, per minute and per hour	Rate-limiting plugins; per tool not stated	Not stated	Platform limits per organization	Plan task allowance
Audit log of tool calls	Every call, with input, output and status	Yes, plugin audit log	Call logging; governance audit logs with a paid licence	Tool-call traces	Activity history and account audit log
Single sign-on	OIDC and SCIM, self-hosted Enterprise	OIDC or SAML for Konnect, Enterprise	Not stated	SAML or OIDC and SCIM, Enterprise	SAML, Enterprise

From each vendor's public documentation, checked in November 2026. “Not stated” means we found no public statement, not that the feature is missing. Products change quickly: check the vendor's own pages before you decide.

Sources: Kong AI MCP Proxy · Kong pricing · Kong Konnect regions · Docker MCP Gateway · Docker MCP Catalog and Toolkit · Composio pricing · Composio custom MCP · Zapier MCP · Zapier MCP security

When AnythingMCP is not the right fit: if you need a single SaaS integration for personal use, an existing MCP server from the registry is lighter. And if your team has already standardised on another hosted gateway, you probably don't need AnythingMCP.

See detailed comparisons

Deployment options

The same open-source code runs in both places, and connectors work the same way in each.

Self-hosted with Docker

Free under AGPL-3.0 for any use, including commercial use, up to 3 active users. More users, single sign-on, SCIM and support come with Enterprise. Run it on your own servers or in your private cloud, next to on-prem databases and SOAP services. Credentials, audit log and knowledge graph stay in your PostgreSQL.

View on GitHub

AnythingMCP Cloud (EU)

Operated by us in Frankfurt, Germany. Nothing to install or patch: start with a 7-day free trial and connect your first system in minutes.

Start free trial

Compare plans and prices

MCP gateway FAQ

Is AnythingMCP an open-source MCP gateway?

Yes. The gateway, dashboard and connectors are on GitHub under the AGPL-3.0 licence. The self-hosted Community edition is free for any use, including commercial use, up to 3 active users, with unlimited connectors. More users, single sign-on, SCIM, File Search beyond the 30-day trial and support come with Enterprise, on request. If you modify AnythingMCP and offer it to others as a network service, the AGPL asks you to share those changes. A commercial licence without that obligation is also available.

Can I self-host the MCP gateway?

Yes. AnythingMCP runs with Docker on your own servers, and the repository documents Docker Compose, Railway and DigitalOcean. Self-hosting is the usual choice when the gateway has to reach systems inside your network, or when credentials and logs must not leave your infrastructure.

Does it work with Claude, ChatGPT, Copilot and Cursor?

Yes. The gateway exposes standard remote MCP endpoints, so any client that supports remote MCP servers can connect, including Claude (as a custom connector), ChatGPT, Copilot and Cursor. Which plans can add custom MCP servers is decided by each vendor; our client guides show the current steps.

How is an MCP gateway different from an API gateway?

An API gateway manages HTTP traffic between applications: routing, rate limits, keys. An MCP gateway speaks the Model Context Protocol to AI agents: it publishes tools with names, descriptions and input schemas a model can understand, decides which tools each user sees, and logs every tool call. The two work together: AnythingMCP can call APIs that sit behind your existing API gateway.

Does it support SOAP services and on-prem databases?

Yes. A WSDL is turned into one MCP tool per SOAP operation, with WS-Security, basic auth and client certificates. Databases (PostgreSQL, MySQL, MariaDB, MSSQL, Oracle, MongoDB, SQLite) can be connected with a read-only account. For systems inside your network, self-host the gateway next to them; the cloud can only reach systems that are reachable from the internet.

Where is my data stored?

When you self-host, everything stays on your infrastructure: credentials (AES-256-GCM encrypted), the audit log and the knowledge graph live in your own PostgreSQL database. On AnythingMCP Cloud the same data is stored in Frankfurt, Germany, and a data processing agreement (DPA) is available. Tool results you pass to an AI assistant are processed by that assistant's vendor under its own terms.

How does AnythingMCP compare with Kong, Docker MCP Gateway, Composio and Zapier MCP?

Kong and Docker MCP Gateway put one endpoint, access rules and logging in front of MCP servers you already run; Kong can also turn REST routes into tools. Composio and Zapier MCP are hosted services with large catalogs of SaaS actions. AnythingMCP also builds the tools from your own REST, SOAP, GraphQL and SQL systems, governs them per role and per tool, and runs self-hosted or in Frankfurt. The comparison table on this page lists what each vendor documents.

Put one gateway in front of your AI tools

Try it on your own APIs in the cloud, or run it on your own servers today.