MCP.so
Sign In
Servers

MetaMCP MCP Server

@metatool-ai

MCP Server MetaMCP manages all your other MCPs in one MCP.

Overview

What is MetaMCP MCP Server?

MetaMCP MCP Server is a proxy server that joins multiple MCP servers into one. It fetches tool, prompt, and resource configurations from MetaMCP App and routes requests to the correct underlying server. It is compatible with any MCP client and provides a multi-workspaces layer for one-click switching between sets of MCP configurations.

How to use MetaMCP MCP Server?

Install via Smithery (npx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude) or manually by setting the METAMCP_API_KEY environment variable and running npx -y @metamcp/mcp-server-metamcp@latest. Configure the transport type (stdio, SSE, or streamable-http) and port using CLI options. Optionally, set METAMCP_API_BASE_URL for the MetaMCP API base URL.

Key features of MetaMCP MCP Server

  • Compatible with any MCP client.
  • Multi-workspaces layer for one-click MCP config switching.
  • GUI dynamic updates of MCP configurations.
  • Namespace isolation for joined MCP servers.
  • Supports stdio, SSE, and Streamable HTTP transports.

Use cases of MetaMCP MCP Server

  • Centralize management of multiple MCP servers under a single proxy.
  • Switch between different sets of MCP configurations without restarting the client.
  • Provide a unified interface while isolating underlying MCP server namespaces.
  • Dynamically update MCP configurations via the MetaMCP App GUI.

FAQ from MetaMCP MCP Server

Is this package deprecated?

Yes. This local proxy package is deprecated in MetaMCP’s 2.0 all-in-one architecture. Please check the new repository at https://github.com/metatool-ai/metamcp.

How do I install MetaMCP MCP Server?

Install via Smithery (using @smithery/cli install @metatool-ai/mcp-server-metamcp) or manually by running npx -y @metamcp/mcp-server-metamcp@latest with the METAMCP_API_KEY environment variable set.

What transports does it support?

It supports stdio (default), SSE (via --transport sse), and Streamable HTTP (via --transport streamable-http). For SSE and Streamable HTTP, specify a port with --port (default 12006).

How do I handle stderr from child MCP processes

More from Other