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.

1. Click on "Install Server".

2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.

3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MetaMCP MCP Server list all available tools from my connected MCP servers"

That's it! The server will respond to your query, and you can continue using it as needed.

Here is a step-by-step guide with screenshots.

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

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

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

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

mcp-server-metamcp --metamcp-api-key <your-api-key> --transport streamable-http --port 12006

mcp-server-metamcp --metamcp-api-key <your-api-key> --transport sse --port 12006 --use-docker-host

# Use inherit to see stderr output from child processes
mcp-server-metamcp --metamcp-api-key <your-api-key> --stderr inherit

# Use pipe to capture stderr (default is ignore)
mcp-server-metamcp --metamcp-api-key <your-api-key> --stderr pipe

# Or set via environment variable
METAMCP_STDERR=inherit mcp-server-metamcp --metamcp-api-key <your-api-key>

Options:
 --metamcp-api-key <key> API key for MetaMCP (can also be set via METAMCP_API_KEY env var)
 --metamcp-api-base-url <url> Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)
 --report Fetch all MCPs, initialize clients, and report tools to MetaMCP API
 --transport <type> Transport type to use (stdio, sse, or streamable-http) (default: "stdio")
 --port <port> Port to use for SSE or Streamable HTTP transport, defaults to 12006 (default: "12006")
 --require-api-auth Require API key in SSE or Streamable HTTP URL path
 --stateless Use stateless mode for Streamable HTTP transport
 --use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)
 --stderr <type> Stderr handling for STDIO transport (overlapped, pipe, ignore, inherit) (default: "ignore")
 -h, --help display help for command

# Install dependencies
npm install

# Build the application
npm run build

# Watch for changes
npm run watch

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

Looking for Admin?