MCP Server MetaTool

What is MCP Server MetaTool?

MCP Server MetaTool is a proxy server that joins multiple MCP servers and forwards tool calls to the appropriate server. It should be used with metatool-app, the GUI tool manager for MCP. It is both a MCP client and a MCP server, aggregating tool lists from multiple servers with namespace isolation.

How to use MCP Server MetaTool?

Set the METATOOL_API_KEY environment variable (obtain from metatool‑ai/metatool‑app) and optionally METATOOL_API_BASE_URL to point to another metatool instance. Then run uvx mcp-server-metatool. A MCP client (e.g., Claude Desktop) must connect to this server.

Key features of MCP Server MetaTool

• Acts as both MCP client and server
• Aggregates tools from multiple MCP servers
• Provides namespace isolation on tool lists
• Forwards tool calls to the appropriate server
• Integrates with the metatool‑app GUI

Use cases of MCP Server MetaTool

• Managing multiple MCP servers through a single proxy
• Using metatool‑app as a central GUI for MCP server configurations
• Aggregating tools from various MCP sources for a client like Claude Desktop

FAQ from MCP Server MetaTool

Is MCP Server MetaTool still maintained?

No, this repo is deprecated and no longer maintained. A Node.js substitute with better performance is available at metatool‑ai/mcp‑server‑metamcp.

What dependencies are required to run MCP Server MetaTool?

It requires uv (for running via uvx) and a running instance of metatool‑app (self‑hostable and free) to supply the API key and server configurations.

Where does the data reside?

The server connects to the metatool‑app API to get a list of MCP servers to connect to. No other data persistence is mentioned.

What transport or authentication does it use?

Authentication is via a METATOOL_API_KEY environment variable. Transport is not explicitly specified but is handled by uvx (likely stdio).

Do I need a MCP client to use it?

Yes, you need a MCP Client (e.g., Claude Desktop) to connect to this server.