metamcp vs toolsdk-mcp-registry
MCP server gateways compared
metamcp combines configured MCP servers into namespace-controlled endpoints, while toolsdk-mcp-registry adds a structured catalog for discovering and running MCP servers. Both are TypeScript projects with self-hosting options, but metamcp emphasizes endpoint configuration and tool controls, whereas toolsdk-mcp-registry emphasizes discovery, API access, and sandboxed execution.

metamcp: Combine MCP Servers Behind One Gateway
MetaMCP combines configured MCP servers into unified endpoints and applies namespace-level controls. It suits teams hosting and managing MCP tools for multiple clients, but its development is currently quiet and recent pull-request activity is absent.

toolsdk-mcp-registry: Discover and Run MCP Servers Through One Gateway
ToolSDK MCP Registry is a structured catalog and gateway for discovering MCP servers and connecting AI applications to their tools. Built with TypeScript, it supports STDIO and Streamable HTTP servers, self-hosting, sandbox execution, and OAuth 2.1 flows.
| metamcp | toolsdk-mcp-registry | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Stars | 2.7k | 222 |
| Forks | 436 | 818 |
| Last analyzed | Oct 9, 2026 | Nov 7, 2026 |
Key differences
- metamcp aggregates tools, resources, and prompts from configured servers; toolsdk-mcp-registry catalogs servers and offers an API to inspect, discover, and execute tools.
- metamcp organizes endpoints into namespaces with controls for server and tool exposure and metadata overrides; toolsdk-mcp-registry organizes catalog entries by category and combines private entries with the official MCP Registry in search.
- metamcp supports SSE and Streamable HTTP endpoints; toolsdk-mcp-registry connects local STDIO packages and remote Streamable HTTP servers.
- metamcp offers API-key authentication or MCP OAuth; toolsdk-mcp-registry supports OAuth 2.1 proxy flows and optional sandbox integrations such as Sandock, Daytona, and E2B.
- Both use TypeScript, MIT licensing, and Docker Compose deployment; toolsdk-mcp-registry’s Compose setup includes Meilisearch, while metamcp requires Node.js 18 or later and recommends 2 to 4 GB of memory for online deployment.
- metamcp’s recent development activity is quiet and concentrated around one contributor; toolsdk-mcp-registry has regular commits and merged pull requests with a broader contributor base, though it has had no releases in the last year and no issues closed recently.
Choose metamcp if you…
- need to bundle configured MCP servers into namespace-specific endpoints with controls over exposed tools.
- want to adjust tool names, descriptions, and annotations or apply middleware to MCP requests and responses.
- prefer SSE support and API-key authentication or MCP OAuth for external endpoints.
Choose toolsdk-mcp-registry if you…
- need a structured catalog and search for discovering MCP servers, including private entries alongside the official registry.
- want an HTTP API or SDK to inspect servers, discover tools, and execute them.
- need to connect local STDIO packages and remote Streamable HTTP servers, with optional sandbox execution or OAuth 2.1 flows.
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.