Adamwattis MCP Proxy Server

🚀 MCP Proxy Server

A proxy server that aggregates and provides access to multiple MCP resource servers. It centralizes the management of multiple MCP resource servers through a unified interface.

This server acts as a central hub that can:

• Connect to and manage multiple MCP resource servers.
• Expose their combined capabilities through a unified interface.
• Route requests to the appropriate backend servers.
• Aggregate responses from multiple sources.

✨ Features

Resource Management

• Discover and connect to multiple MCP resource servers.
• Aggregate and retrieve resources from all connected servers.
• Maintain a consistent URI scheme across servers.
• Handle resource routing and resolution.

Tool Aggregation

• Expose tools from all connected servers.
• Route tool invocations to the appropriate backend servers.
• Maintain tool state and handle responses.

Prompt Handling

• Aggregate prompts from all connected servers.
• Route prompt requests to the appropriate backends.
• Handle prompt responses from multiple servers.

📦 Installation

To use with Claude Desktop, add the server configuration:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-proxy": {
      "command": "/path/to/mcp-proxy-server/build/index.js",
      "env": {
        "MCP_CONFIG_PATH": "/absolute/path/to/your/config.json"
      }
    }
  }
}

Debugging

Since MCP servers communicate via stdio, debugging can be challenging. We recommend using MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access the debugging tools. Open it in your browser.

📚 Documentation

Configuration

The server requires a JSON configuration file specifying the MCP servers to connect to. Copy the example configuration and modify it as needed:

cp config.example.json config.json

Example configuration structure:

{
  "servers": [
    {
      "name": "Server 1",
      "transport": {
        "command": "/path/to/server1/build/index.js"
      }
    },
    {
      "name": "Server 2",
      "transport": {
        "command": "server2-command",
        "args": ["--option1", "value1"]
      }
    }
  ]
}

The configuration file must be provided when running the server:

MCP_CONFIG_PATH=./config.json mcp-proxy-server

Development

Install dependencies:

npm install

Build the server:

npm run build

Develop with automatic rebuild:

npm run watch