anythingmcp vs mcp-gateway
MCP gateways for APIs and tools compared
anythingmcp and mcp-gateway both let AI clients access tools through an MCP endpoint. anythingmcp focuses on generating tools from business systems and databases, while mcp-gateway focuses on routing and discovering tools across MCP servers and REST APIs.
anythingmcp: Turn APIs and Databases into MCP Tools
AnythingMCP is a self-hosted, TypeScript MCP gateway that turns REST/OpenAPI, SOAP, GraphQL, OData and SQL systems into tools for Claude, ChatGPT, Copilot and other MCP clients. It combines ready-made connectors with access controls and auditing.
mcp-gateway: Route MCP Servers and REST APIs Through One Endpoint
A Rust gateway that brings MCP servers and REST APIs behind one endpoint, with tools discovered on demand through a compact meta-tool surface. It also bridges MCP protocol revisions and adds centralized routing and policy controls.
| anythingmcp | mcp-gateway | |
|---|---|---|
| Language | TypeScript | Rust |
| License | AGPL-3.0 | NOASSERTION |
| Stars | 759 | 78 |
| Forks | 109 | 19 |
| Last analyzed | Oct 29, 2026 | Oct 3, 2026 |
Key differences
- anythingmcp generates connectors for systems including SOAP, GraphQL, OData, SQL, and MongoDB; mcp-gateway aggregates MCP backends and imports REST capabilities from OpenAPI specifications.
- anythingmcp exposes assigned tools through MCP endpoints, while mcp-gateway offers meta-tools to search for and invoke backend tools on demand.
- anythingmcp is written in TypeScript and uses the AGPL-3.0 license; mcp-gateway is written in Rust and its metadata reports NOASSERTION, with commercial use described as requiring a commercial license.
- anythingmcp includes tool-level response mapping, database query tools that are read-only by default, and an audit log; mcp-gateway includes transport options, protocol revision bridging, rate limiting, and a web UI.
- The listed project counts are 810 stars and 82 forks for anythingmcp, compared with 78 stars and 19 forks for mcp-gateway.
Choose anythingmcp if you…
- need to generate tools from business APIs, databases, or services such as SOAP and OData.
- want role-based access, response-field controls, and auditing for tool calls.
- prefer a self-hosted gateway for connecting company systems to AI clients.
Choose mcp-gateway if you…
- need to route multiple MCP servers and REST APIs through one endpoint.
- want clients to discover and invoke tools on demand through a compact meta-tool surface.
- need transport choices or a bridge between supported MCP protocol revisions.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.