What is Metatool Ai Mcp Server Metamcp

MetaMCP MCP Server is a proxy server that consolidates multiple MCP servers into a single interface. It retrieves configurations for tools, prompts, and resources from the MetaMCP App and directs requests to the appropriate underlying server.

Use cases

Use cases include managing different tool configurations for software projects, enabling quick switching between different environments for testing, and providing a unified interface for accessing various MCP resources.

How to use

To use MetaMCP MCP Server, you can install it via Smithery using the command: npx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude. Alternatively, for manual installation, set the environment variable METAMCP_API_KEY and run npx -y @metamcp/mcp-server-metamcp@latest.

Key features

Key features include compatibility with any MCP client, a multi-workspaces layer for easy switching between MCP configurations, dynamic GUI updates for MCP configurations, and namespace isolation for joined MCPs.

Where to use

MetaMCP MCP Server can be used in various fields that require the management of multiple MCPs, such as software development, data processing, and any environment where multiple configurations need to be managed seamlessly.

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:

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>"
      }
    }
  }
}

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:

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

For help with 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-mcp-server as MetaMCP MCP Server
    participant MetaMCPApp as MetaMCP App
    participant MCPServers as Installed MCP Servers in Metatool App

    MCPClient ->> MetaMCP-mcp-server: Request list tools
    MetaMCP-mcp-server ->> MetaMCPApp: Get tools configuration & status
    MetaMCPApp ->> MetaMCP-mcp-server: Return tools configuration & status

    loop For each listed MCP Server
        MetaMCP-mcp-server ->> MCPServers: Request list_tools
        MCPServers ->> MetaMCP-mcp-server: Return list of tools
    end

    MetaMCP-mcp-server ->> MetaMCP-mcp-server: Aggregate tool lists
    MetaMCP-mcp-server ->> MCPClient: Return aggregated list of tools

    MCPClient ->> MetaMCP-mcp-server: Call tool
    MetaMCP-mcp-server ->> MCPServers: call_tool to target MCP Server
    MCPServers ->> MetaMCP-mcp-server: Return tool response
    MetaMCP-mcp-server ->> MCPClient: Return tool response

Credits

• Inspirations and some code (refactored in this project) from https://github.com/adamwattis/mcp-proxy-server/