MCP Server Metamcp

🚀 MetaMCP MCP Server

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

https://metamcp.com: Your one-stop management platform for MCP.

MetaMCP application repository: https://github.com/metatool-ai/metatool-app

🚀 Quick Start

✨ Features

• Multifunctional Proxy: MetaMCP MCP Server supports multiple transport protocols, including standard input/output and SSE.
• Easy Integration: Multiple MCP services can be integrated into a unified interface through simple configuration.
• High Performance: The request routing mechanism is optimized to ensure efficient handling of a large number of concurrent requests.

📦 Installation

Install using Smithery

Sometimes Smithery may work properly (tested locally on Windsurf). However, due to the special nature of MetaMCP, which runs other MCPs on it, if instability occurs, consider manual installation.

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

💻 Usage Examples

Basic Usage (Standard Input/Output Mode - Default)

mcp-server-metamcp --metamcp-api-key <your API key>

Advanced Usage (SSE Mode)

mcp-server-metamcp --metamcp-api-key <your API key> --transport sse --port 12006

After enabling the SSE transport option, the server will start an Express.js web server, listening for SSE connections at the /sse endpoint and accepting messages at the /messages endpoint.

Command-line Options

• --metamcp-api-key: Specify the access key for the MetaMCP API.
• --transport: Select the transport protocol (default is stdio).
• --port: Specify the port to which the server binds (default is 3000).

Environment Variables

Configure the server behavior by setting the following environment variables:

• METAMCP_API_KEY: Required. The access key for the MetaMCP API.
• TRANSPORT: Optional. Default is stdio. Supported values include http and sse.

🔧 Technical Details

Architecture Overview

Diagram

graph TD
    A[MetaMCP MCP Server] --> B[Client]
    A --> C[Target MCP Servers]
    B -> A: Call Tool
    A -> C: call_tool to target MCP Server
    C -> A: Return tool response
    A -> B: Return tool response

Description

1. Client Request: The client sends a tool call request to the MetaMCP MCP Server.
2. Routing Logic: The MetaMCP MCP Server forwards the request to the corresponding target MCP server based on the preset routing rules.
3. Response Handling: The target MCP server returns a response, and the MetaMCP MCP Server passes it to the client after receiving it.

📄 License

This project is inspired by and partially based on the code from https://github.com/adamwattis/mcp-proxy-server/ (refactored in this project).