MCP Coordinator

Exposes three tools to Claude and dynamically loads MCPs on demand to minimize token usage.

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 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": {
    "cyberclash-mcp_coordinator": {
      "command": "node",
      "args": [
        "C:\\path\\to\\mcp_coordinator\\build\\index.js"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN"
      }
    }
  }
}

The MCP Coordinator is a proxy that exposes only a small set of tools to Claude while dynamically loading and routing to many underlying MCP servers. This keeps your conversations lean by reducing the number of tool definitions loaded into context, yet still gives you access to all MCP capabilities on demand.

How to use

Use the MCP Coordinator when you want to access multiple MCPs without loading all their tools into your context window. You interact with three core tools to list MCPs, inspect their available tools, and call a specific tool on a chosen MCP. The coordinator loads the requested MCP on demand, executes the tool, and returns only the result, keeping your dialogue concise.

How to install

Prerequisites you need before installing include Node.js and npm (or a compatible Node toolchain). Ensure you have a supported shell or terminal to run commands.

# Install dependencies
npm install

# Build TypeScript
npm run build

# Copy manifest to build folder (if your workflow requires it)
cp src/manifest.json build/manifest.json

Additional sections

Configuration and usage details are provided below to help you set up the coordinator with Claude Desktop, Claude Code, and global settings. The coordinator itself does not require API keys, but you can pass environment variables for MCPs that need authentication (for example, a GitHub token) so those credentials can be used by the MCPs you load.

The coordinator exposes the following tools you can call from Claude:

list_mcps
get_mcp_tools
call_mcp_tool

Environment variables you can provide to the coordinator will be passed to child MCPs via the ${VAR_NAME} syntax in their manifests. Use this to supply tokens or other secrets only to MCPs that require them.

Available tools

list_mcps

List all available MCP servers and their descriptions from the manifest.

get_mcp_tools

Get the list of tools available in a specific MCP server, including tool names, descriptions, and input schemas.

call_mcp_tool

Call a specific tool on an MCP server by providing the server name, tool name, and optional tool arguments. Returns the result from the MCP tool call.