mcp -metatool

MetaTool MCP Server is a proxy that joins multiple MCP servers and forwards tool calls to the appropriate backend MCP server. It operates as both an MCP client and server, connecting to the Metatool App to discover MCP servers and then aggregating tool lists from those servers with namespace isolation. When a client requests the list of tools, MetaTool aggregates tools from all connected MCP servers and presents a unified view. When a tool is invoked, the call is forwarded to the target MCP server responsible for that tool, and the response is returned to the client. This setup is intended to work in conjunction with the Metatool App, which manages the MCP server configurations and status, providing a cohesive tool management experience across multiple MCP backends.

Prerequisites:

• Python with uv (the uvx runner) installed or available in your environment
• Access to the Internet to install/resolve dependencies via uvx
• METATOOL_API_KEY from metatool-app (required for API access)

Installation steps:

1. Install/prepare uvx (Python-based MCP runner):

   • Ensure Python is installed on your system.
   • Install uvx if not already available (usually via pipx or your environment's package manager).

2. Set required environment variables:

   • In your shell, export the required API key: export METATOOL_API_KEY="your_api_key_from_metatool-app"
   • Optionally, set a base URL for the metatool instance you want to connect to: export METATOOL_API_BASE_URL="http://localhost:12005"

3. Run the MetaTool MCP Server:

   • Start the server using uvx: uvx mcp-server-metatool

4. Verify the server starts and appears in your Metatool App configuration, then connect a MCP Client to the MetaTool MCP server to enumerate and invoke tools.

Notes and tips:

• The MetaTool MCP Server relies on the Metatool App API; ensure METATOOL_API_KEY is valid and that the base URL (if provided) points to a reachable Metatool instance.
• If you modify environment variables, restart the MCP server so changes take effect.
• This repository is deprecated in favor of newer Node.js-based implementations; performance and bug fixes may be present in successor projects.
• If you encounter connection issues, verify network access between the MCP client, the MetaTool MCP Server, and the Metatool App API endpoints.
• The mcp_config example uses the uvx runner; adapt commands if you are using a different runtime or deployment method.
• When deploying multiple MCP servers through MetaTool, ensure each backend MCP server is reachable and properly namespaced to avoid tool collisions.