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.
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 databasesExisting 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
251 ready-made connectors for ERP, accounting, CRM, e-commerce, logistics and more, installed in a few clicks.
Browse the marketplaceOAuth 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 AnythingMCPSSO 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. Included free in every self-hosted install; 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.
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.
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.
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, including commercial use inside your own company. 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 GitHubAnythingMCP 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 trialMCP gateway FAQ
Is AnythingMCP an open-source MCP gateway?
Yes. The gateway, dashboard and connectors are on GitHub under the AGPL-3.0 licence. Self-hosting is free, with unlimited connectors, and commercial use inside your own company is included. 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 also documents Helm, 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.
Related pages
SOAP, WSDL and on-prem databases
How the gateway handles legacy enterprise systems.
Custom Claude connectors
Turn any API into a Claude connector without code.
ChatGPT apps and connectors
The MCP backend for ChatGPT connectors and apps.
Connector marketplace
Ready-made connectors you install in a few clicks.
Who builds AnythingMCP
The team, the company and how we work.
Community Edition
Self-host the whole stack in a few minutes.
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.