Our take
Quietno commits in the last 90 days- Activity
- 35
- Community
- 44
- Issues
- 40
- Pull requests
- 20
+50 stars in the last 30 days
- Slower to close issues than 82% of the projects we track
MetaMCP has a broad, practical feature set for self-hosted MCP gateway management, but its quiet recent development and highly concentrated contributions make maintenance continuity an important adoption consideration.
Good fit if
- You need to combine MCP servers, curate their tools, and serve them through shared endpoints.
- Your team can deploy and operate a Docker Compose application with Node.js-based components.
- You are comfortable with the MIT license and can assess the project's maintenance pace for your deployment.
Look elsewhere if
- You need evidence of active recent development: the project has had no commits in the last 90 days and no merged pull requests in that period.
- Your organization requires contributions and maintenance to be broadly distributed, since most recorded contributions come from one person.
- You need a feature the README describes as planned, such as a headless admin API or additional middleware.
All health signals
| Last commit | 2026-06-22 (4 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 3 (latest v2.4.22, 2025-12-19) |
| Contributors | 28 (top contributor: 84% of commits) |
| Issues closed, last 90 days | 4 (typically closed in 56 days) |
| Pull requests merged, last 90 days | 0 |
| Project age | 21 months |
Checked on 2026-10-09 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
2,762Forks
450Change since Nov 17, 2026: +1 stars·-1 forks
Overview
MetaMCP is a self-hosted MCP gateway that combines multiple MCP server configurations into one MCP server endpoint. It addresses the operational overhead of connecting clients to separate servers by letting teams group servers into namespaces, choose which tools to expose, and serve the result over supported transports.
It is aimed at teams building or operating MCP-based applications that want a single place to configure access, authentication, and tool metadata. The project is a TypeScript web application with a Docker Compose deployment path, rather than a small standalone proxy library.
Key Features
- Aggregate tools, resources, and prompts from configured MCP servers into a unified endpoint.
- Organize servers into namespaces, with controls to enable or disable servers and individual tools.
- Expose endpoints over SSE or Streamable HTTP, and provide OpenAPI endpoints for compatible clients.
- Configure API-key authentication or MCP OAuth for external endpoint access.
- Override tool names, titles, descriptions, and annotations at the namespace level.
- Apply middleware to MCP requests and responses, including a built-in filter for inactive tools.
- Manage server configurations with a built-in inspector, and configure OIDC sign-in for the web application.
Use Cases
- An MCP platform team can bundle several internal servers into a smaller set of endpoints for application developers.
- A team supporting multiple MCP clients can use shared endpoints and authentication instead of maintaining separate server connections per client.
- Operators can create different namespaces for teams or tasks, exposing only the tools each endpoint needs.
- Developers can inspect configured MCP servers and adjust tool metadata before making an aggregated endpoint available to users.
What you need
Detected in the repository
- Node.js >=18 (from package.json)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
git clone https://github.com/metatool-ai/metamcp.git
cd metamcp
cp example.env .env
docker compose up -d
See the README and documentation for configuration and client connection details.
Alternatives
- MCPJungle: MCPJungle offers shared server discovery, access control, and observability, while MetaMCP emphasizes unified endpoints with namespace-level controls.
- mcphub: MCPHub adds credential management, logs, and health monitoring to its gateway, while MetaMCP focuses on combining servers into controlled namespaces.
- mcp-gateway: mcp-gateway also routes REST APIs and bridges MCP protocol revisions, exposing tools on demand through a compact meta-tool surface.
- magictunnel: MagicTunnel uses a single natural-language tool to discover and invoke other tools, and includes a dashboard and service supervisor.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| metamcp | TypeScript | MIT | 2.7k | Quiet |
| MCPJungle | Go | MPL-2.0 | 1.3k | Active |
| mcphub | TypeScript | Apache-2.0 | 2.5k | Active |
| mcp-gateway | Rust | Other | 78 | Active |
| magictunnel | Rust | – | 259 | Inactive |
Considerations
- The health data marks the project Quiet: there have been no commits in the last 90 days, no pull requests merged in that period, and the latest listed release is from December 2025. Issues are still being closed, but the median close time is measured in weeks.
- Contribution activity is concentrated, with most of the code attributed to one person. Teams adopting it should consider how they would handle fixes or maintenance if that contributor is unavailable.
- Deployment needs include Docker and Compose, and the application requires Node.js 18 or later. The README recommends a server with 2 to 4 GB of memory for online deployment.
- The README labels more middleware, a headless admin API, and dynamic tool-selection features as future work. Confirm that the current feature set covers your needs.
- The repository uses the MIT license. Review its terms as part of your organization's software approval process.
Found this useful?
Share it with someone who would like metamcp.