Metatool

Proxies and aggregates tools from multiple MCP servers for unified access via a single MetaTool client.

javascript

5

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "metatool-ai-mcp-server-metatool": {
      "command": "uvx",
      "args": [
        "mcp-server-metatool"
      ],
      "env": {
        "METATOOL_API_KEY": "YOUR_API_KEY",
        "METATOOL_API_BASE_URL": "http://localhost:12005"
      }
    }
  }
}

You can run an MCP Server that acts as a proxy to multiple MCP servers, aggregating tool lists and routing tool calls to the correct backend. This makes it easy to manage multiple MCP endpoints from a single entry point, while keeping tools namespaced and organized.

How to use

You connect to the MetaTool MCP Server from your MCP client. Start the MCP server process, ensuring you provide the required API key so the server can authenticate with the metatool API. Once running, your MCP client can request the available tools, and MetaTool will fetch and aggregate tool lists from all connected MCP servers. When you call a tool, the request is forwarded to the appropriate underlying MCP server, and the response is returned to you.

How to install

Prerequisites: you need a runtime capable of executing the MCP server, typically a Node.js environment and the uvx runtime available on your system.

Step 1: Set up your API key and (optionally) the base URL for the metatool API.

export METATOOL_API_KEY="YOUR_API_KEY"
export METATOOL_API_BASE_URL="http://localhost:12005"  # optional; point to another metatool instance

Step 2: Run the MCP server with the provided runtime command.

uvx mcp-server-metatool

Additional configuration and notes

The server uses two environment variables can be configured: METATOOL_API_KEY (required) to authorize with the metatool API, and METATOOL_API_BASE_URL (optional) to point to another metatool instance. You can set these variables in your shell before starting the server or in your deployment environment.

Tools and endpoints

The server aggregates and forwards tool-related calls across all connected MCP servers. It supports listing tools from multiple sources and routing tool calls to the correct server based on namespace handling.

Available tools

list_tools

Fetch and aggregate the list of available tools from all connected MCP servers, with namespace isolation to avoid conflicts.

call_tool

Forward a tool invocation to the appropriate underlying MCP server and return its response.

aggregate_tool_lists

Combine tool lists from multiple MCP servers into a single consolidated list for the client.