MCP Server MetaTool

Catalog onlyCatalog onlySTDIO

Overview

MCP Server MetaTool is a proxy server designed to connect multiple MCP servers and forward tool calls to the appropriate server, enhancing the management of tools across different servers.

To use MCP Server MetaTool, you need to install it and set up the necessary environment variables, including the METATOOL_API_KEY. It works in conjunction with the Metatool App, which serves as the GUI tool manager for MCP.

Aggregates tool lists from multiple MCP servers. - Forwards tool calls to the correct MCP server. - Supports namespace isolation for tools.

Managing tools across multiple MCP servers seamlessly.
Simplifying the process of tool calls in a multi-server environment.
Enhancing the functionality of the Metatool App by providing a unified interface for tool management.

Add to your AI client

Use these steps to connect MCP Server MetaTool in Cursor, Claude, VS Code, and other MCP-compatible apps. The same JSON appears in the Use with menu above for one-click copy.

Cursor

Add this to your .cursor/mcp.json file in your project root, then restart Cursor.

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server-metatool-metatool-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-server-metatool-metatool-ai"
      ]
    }
  }
}

Claude Desktop

Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "mcp-server-metatool-metatool-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-server-metatool-metatool-ai"
      ]
    }
  }
}

Claude Code

Add this to your project's .mcp.json file. Claude Code will detect it automatically.

.mcp.json (project root)

{
  "mcpServers": {
    "mcp-server-metatool-metatool-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-server-metatool-metatool-ai"
      ]
    }
  }
}

VS Code (Copilot)

Add this to your .vscode/mcp.json file. Requires the GitHub Copilot extension with MCP support enabled.

.vscode/mcp.json

{
  "servers": {
    "mcp-server-metatool-metatool-ai": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-server-metatool-metatool-ai"
      ]
    }
  }
}

Windsurf

Add this to your Windsurf MCP config file, then restart Windsurf.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-server-metatool-metatool-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-server-metatool-metatool-ai"
      ]
    }
  }
}

Cline

Open Cline settings, navigate to MCP Servers, and add this server configuration.

Cline MCP Settings (via UI)

{
  "mcpServers": {
    "mcp-server-metatool-metatool-ai": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-mcp-server-metatool-metatool-ai"
      ]
    }
  }
}

FAQ

What is required to run MCP Server MetaTool?

You need to set the METATOOL_API_KEY and have a compatible MCP Client to connect to the server.

Is MCP Server MetaTool free to use?

Yes! It is open source and free to use.

Can I customize the server connection?

Yes! You can set the METATOOL_API_BASE_URL to point to another Metatool instance.

Developer tools