MetaMCP provides a unified middleware layer for managing multiple MCP (Model Communication Protocol) servers, enabling seamless integration and context management for various AI clients like Claude Desktop and Cursor. It offers a self-hostable GUI application and a local proxy, allowing users to aggregate tools, prompts, and resources across different MCP servers and workspaces, preventing context pollution and enabling granular control.

How It Works

MetaMCP operates as an MCP server itself, acting as a central hub. It communicates with a local proxy that interfaces with installed MCP servers. The GUI application manages configurations, tool toggles, and workspace switching. When an MCP client requests tools, the MetaMCP proxy aggregates tool lists from all configured MCP servers, presenting a unified interface to the client. Tool calls are then routed to the appropriate underlying MCP server.

Quick Start & Requirements

• Install: git clone https://github.com/metatool-ai/metatool-app.git && cd metatool-app && cp example.env .env && docker compose up --build -d
• Prerequisites: Docker, npx, uvx (recommended). Requires an MCP Client (e.g., Claude Desktop, Cursor) configured to connect to the MetaMCP server.
• Access: http://localhost:12005
• Docs: https://metamcp.com/

Highlighted Details

• Supports any MCP client by acting as an MCP server.
• Enables multi-workspace management to isolate contexts.
• Allows tool-level toggling for fine-grained control.
• Offers both a free cloud version and a self-hostable open-source option.

Maintenance & Community

The project is maintained by metatool-ai. Demo videos are available at https://metamcp.com/.

Licensing & Compatibility

• License: GNU AGPL v3.
• Compatibility: The AGPL v3 license may impose copyleft restrictions on derivative works, potentially requiring modifications to be open-sourced if distributed.

Limitations & Caveats

The project mentions a "Credits (Deprecated)" section, suggesting potential past reliance on or integration with a system that is no longer supported. The AGPL v3 license requires careful consideration for commercial or closed-source integrations.