MCP Hub MCP

🚀 MCP-Hub-MCP Server

A hub server that can connect to and manage other MCP (Model Context Protocol) servers.

🚀 Quick Start

This project builds an MCP hub server that can automatically connect to other MCP servers through a configuration file, list their tools, and execute these tools. It's particularly useful for bypassing Cursor's 40-tool MCP limit. Even outside of Cursor, it helps reduce AI errors by hiding infrequently used tools.

✨ Features

• Automatically connect to other MCP servers via a configuration file.
• List available tools on connected servers.
• Invoke tools on connected servers and return results.

📦 Installation

Prerequisites

• Node.js 18.0.0 or higher.
• npm, yarn, or pnpm.

Installation

# Clone the repository
git clone <repository-url>
cd mcp-hub-mcp

# Install dependencies
npm install
# Or
yarn install
# Or
pnpm install

Build

npm run build
# Or
yarn build
# Or
pnpm build

Run

npm start
# Or
yarn start
# Or
pnpm start

Development Mode

npm run dev
# Or
yarn dev
# Or
pnpm dev

📚 Documentation

Configuration

Add the following content to mcp.json:

Using npx

{
  "mcpServers": {
    "other-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-hub-mcp",
        "--config-path",
        "/Users/username/mcp.json"
      ]
    }
  }
}

System Prompt (or Cursor Rule)

Before processing user requests, you must use the "list_all_tools" command to identify available tools.

This ensures that the AI assistant always checks available tools before attempting to use them.

Configuration File

The MCP-Hub-MCP server uses a Claude Desktop format configuration file to automatically connect to other MCP servers. You can specify the configuration file in the following ways:

1. Environment Variable: Set the MCP_CONFIG_PATH environment variable to specify the configuration file path.
2. Command-line Argument: Use the --config-path option to specify the configuration file path.
3. Default Path: Use the mcp-config.json file in the current directory.

Configuration file format:

{
  "mcpServers": {
    "serverName1": {
      "command": "command",
      "args": ["arg1", "arg2", ...],
      "env": { "ENV_VAR1": "value1", ... }
    },
    "serverName2": {
      "command": "another-command",
      "args": ["arg1", "arg2", ...]
    }
  }
}

Example:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Desktop",
        "/Users/username/Downloads"
      ]
    },
    "other-server": {
      "command": "node",
      "args": ["path/to/other-mcp-server.js"]
    }
  }
}

💻 Usage Examples

Basic Usage

The MCP-Hub-MCP server provides the following tools:

1. list-all-tools

Returns a list of tools on all connected servers.

{
  "name": "list-all-tools",
  "arguments": {}
}

2. call-tool

Invoke a specific tool on a particular server.

• serverName: The name of the MCP server on which to invoke the tool.
• toolName: The name of the tool to invoke.
• arguments: Parameters required by the tool.

Request format:

{
  "name": "call-tool",
  "arguments": {
    "serverName": "string",
    "toolName": "string",
    "arguments": {}
  }
}

The response will return the result of the invoked tool.

📋 Submission Specification

Adopt the Conventional Commits specification:

• Type: feat, fix, docs, style, refactor, perf, test.
• Scope: Optional, specify the scope affected by the commit (e.g., server, client).
• Title: A descriptive title, no more than 50 characters.
• Body: Detailed description of the commit content.
• Footer: Optional, include the BREAKING CHANGE label to indicate a breaking change.

🔧 Technical Details

• Node.js
• TypeScript
• @modelcontextprotocol/sdk (Version: ^1.9.0)
• zod (Version: ^3.22.4)

📄 License

MIT