Unified MCP Command Hub

https://metamcp.com: The singular gateway to command all your distributed MCP environments.

This component functions as an intermediary proxy, harmonizing numerous independent MCP instances into a cohesive operational layer. It retrieves the manifest of available functions (tools, prompts, resources) from the central MetaMCP application and dispatches incoming execution requests to the designated host server.

Source repository for the MetaMCP orchestrator utility: https://github.com/metatool-ai/metatool-app

Deployment Procedures

Automated Installation via Smithery

Smithery deployment occasionally encounters transient issues due to MetaMCP's layered architecture (running subordinate MCPs). If automated setup fails, manual installation is recommended.

To initialize the Unified MCP Command Hub automatically using Smithery for Claude Desktop:

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

Manual Setup

Establish the required authentication token first: bash export METAMCP_API_KEY= npx -y @metamcp/mcp-server-metamcp@latest

Configuration for direct execution:

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

Operational Modes

Standard Input/Output (stdio) Operation (Default)

Execute the service using standard streams:

bash mcp-server-metamcp --metamcp-api-key

Server-Sent Events (SSE) Transport Mode

To activate a web interface for data transmission:

bash mcp-server-metamcp --metamcp-api-key --transport sse --port 12006

When using SSE, the service launches an Express.js listener, accepting stream connections on the /sse endpoint and message payloads on the /messages endpoint.

Command Line Interface Directives

Options: --metamcp-api-key Authentication token for the central MetaMCP service (can be sourced from METAMCP_API_KEY environment variable) --metamcp-api-base-url The root URI for the MetaMCP service endpoint (can be sourced from METAMCP_API_BASE_URL environment variable) --report Initiate a full scan of registered MCPs, client initialization, and report status back to the MetaMCP API. --transport Select the communication modality (stdio or sse) (default: "stdio") --port Network port binding for SSE transport (default: "12006") -h, --help Display command usage information

Environment Parameters

• METAMCP_API_KEY: Required access token for the centralized service.
• METAMCP_API_BASE_URL: Specifies the endpoint URI for the MetaMCP backend.

Development Cycle

bash

Install necessary dependencies

npm install

Compile source code

npm run build

Enable continuous compilation upon file modification

npm run watch

Key Attributes

• Universally compatible with virtually ANY MCP Consumer application.
• Multi-Workspace abstraction layer permits instant pivoting between distinct sets of MCP configurations.
• Real-time, GUI-driven updates for configuration parameters.
• Guaranteed operational segregation across integrated MCP domains (Namespace Isolation).

Operational Schematic

mermaid sequenceDiagram participant MCPClient as Client Application (e.g. Desktop UI) participant MetaMCP-mcp-server as Aggregator Proxy Service participant MetaMCPApp as Central Configuration Hub participant MCPServers as Registered Backend MCPs

MCPClient ->> MetaMCP-mcp-server: Request manifest of available utilities
MetaMCP-mcp-server ->> MetaMCPApp: Query for consolidated manifest and status
MetaMCPApp ->> MetaMCP-mcp-server: Deliver aggregated manifest details

loop For every discovered Backend MCP
    MetaMCP-mcp-server ->> MCPServers: Request its specific utility definitions
    MCPServers ->> MetaMCP-mcp-server: Return local utility inventory
end

MetaMCP-mcp-server ->> MetaMCP-mcp-server: Synthesize and merge all utility listings
MetaMCP-mcp-server ->> MCPClient: Present unified utility registry

MCPClient ->> MetaMCP-mcp-server: Trigger execution of a specific function
MetaMCP-mcp-server ->> MCPServers: Forward execution command to the intended target MCP
MCPServers ->> MetaMCP-mcp-server: Return result payload
MetaMCP-mcp-server ->> MCPClient: Relay final execution outcome

Acknowledgements

• Design concepts and preliminary code structures adapted (and heavily refactored) from: https://github.com/adamwattis/mcp-proxy-server/