Metatool Ai MCP Server Metamcp

🚀 MetaMCP MCP Server

A one-stop MCP for managing all MCPs. It integrates multiple MCP servers into one.

https://metamcp.com: A one-stop MCP for managing all MCPs.

The MetaMCP MCP Server is a proxy server that consolidates multiple MCP servers into one. It fetches tool/tip/resource configurations from the MetaMCP application and routes tool/tip/resource requests to the correct underlying servers.

MetaMCP Application Repository: https://github.com/metatool-ai/metatool-app

🚀 Quick Start

📦 Installation

Install via Smithery

Sometimes, Smithery may work properly (confirmed locally on Windsurf). However, since MetaMCP is a special type of server, it may be unstable. If you encounter any issues, consider manual installation.

To automatically install the MetaMCP MCP Server for Claude Desktop via Smithery:

npx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude

Manual Installation

export METAMCP_API_KEY=<env>
npx -y @metamcp/mcp-server-metamcp@latest

{
  "mcpServers": {
    "MetaMCP": {
      "command": "npx",
      "args": ["-y", "@metamcp/mcp-server-metamcp@latest"],
      "env": {
        "METAMCP_API_KEY": "<your api key>"
      }
    }
  }
}

✨ Features

• Compatible with any MCP client.
• Support for one-click switching to another set of MCP configurations across multiple workspace layers.
• Real-time MCP configuration updates via GUI.
• Namespace isolation for jointly running multiple MCPs.

🔧 Technical Details

Environment Variables

Command-line Arguments

You can configure the API key and base URL via command-line arguments:

npx -y @metamcp/mcp-server-metamcp@latest --metamcp-api-key <your-api-key> --metamcp-api-base-url <base-url>

To view all available options:

npx -y @metamcp/mcp-server-metamcp@latest --help

These command-line arguments take precedence over environment variables.

Architecture Overview

sequenceDiagram
    participant MCPClient as MCP Client (e.g., Claude Desktop)
    participant MetaMCP Server
    participant Underlying MCP Server
    
    MCPClient -> MetaMCP Server: Send tool/tip/resource requests
    MetaMCP Server --> Underlying MCP Server: Route requests
    Underlying MCP Server --> MetaMCP Server: Return responses
    MetaMCP Server --> MCPClient: Send back final responses