MetaMCP MCP Server
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Integrations
The README includes a Mermaid sequence diagram to illustrate the architecture of the MetaMCP MCP Server, showing how it interacts with MCP clients, the MetaMCP App, and installed MCP servers.
MetaMCP MCP Server
https://metamcp.com: The One MCP to manage all your MCPs
MetaMCP MCP Server is a proxy server that joins multiple MCP servers into one. It fetches tool/prompt/resource configurations from MetaMCP App and routes tool/prompt/resource requests to the correct underlying server.
MetaMCP App repo: https://github.com/metatool-ai/metatool-app
Installation
Installing via Smithery
Sometimes Smithery works (confirmed in Windsurf locally) but sometimes it is unstable because MetaMCP is special that it runs other MCPs on top of it. Please consider using manual installation if it doesn't work instead.
To install MetaMCP MCP Server for Claude Desktop automatically via Smithery:
Manual Installation
Highlights
- Compatible with ANY MCP Client
- Multi-Workspaces layer enables you to switch to another set of MCP configs within one-click.
- GUI dynamic updates of MCP configs.
- Namespace isolation for joined MCPs.
Environment Variables
- METAMCP_API_KEY: Required. Obtained from MetaMCP App's "API Keys" page (https://metamcp.com/api-keys).
- METAMCP_API_BASE_URL: Optional override for MetaMCP App URL (e.g. http://localhost:12005).
Command Line Arguments
You can configure the API key and base URL using command line arguments:
For help with all available options:
These command line arguments take precedence over environment variables.
Architecture Overview
Credits
- Inspirations and some code (refactored in this project) from https://github.com/adamwattis/mcp-proxy-server/
You must be authenticated.
A proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.