MCP Hub MCP Server

MCP-Hub-MCP Server

A hub server that connects to and manages other MCP (Model Context Protocol) servers.

Overview

This project builds an MCP hub server that can connect to other MCP servers, list their tools, and execute them. It is especially useful for bypassing Cursor’s 40-tool MCP limit. Even outside of Cursor, it helps reduce AI mistakes by hiding infrequently used tools.

Key Features

Automatic connection to other MCP servers via configuration file
List available tools on connected servers
Call tools on connected servers and return results

Configuration

Add this to your mcp.json:

Using npx

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

System Prompt (or Cursor Rules)

Before processing a user's request, you must use the "list_all_tools" command to identify which tools are available.

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

Installation and Running

Requirements

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

Installation

# Clone 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

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:

Environment variable: Set the MCP_CONFIG_PATH environment variable to the configuration file path
Command line argument: Use the --config-path option to specify the configuration file path
Default path: Use mcp-config.json file in the current directory

Configuration file format:

{
  "mcpServers": {
    "serverName1": {
      "command": "command",
      "args": ["arg1", "arg2", ...],
      "env": { "ENV_VAR1": "value1", ... }
    },
    "serverName2": {
      "command": "anotherCommand",
      "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

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

1. `list-all-tools`

Returns a list of tools from all connected servers.

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

2. `call-tool`

Calls a tool on a specific server.

serverName: Name of the MCP server to call the tool from
toolName: Name of the tool to call
toolArgs: Arguments to pass to the tool

{
  "name": "call-tool",
  "arguments": {
    "serverName": "filesystem",
    "toolName": "readFile",
    "toolArgs": {
      "path": "/Users/username/Desktop/example.txt"
    }
  }
}

Commit Message Convention

This project follows Conventional Commits for automatic versioning and CHANGELOG generation.

Format: <type>(<scope>): <description>

Examples:

feat: add new hub connection feature
fix: resolve issue with server timeout
docs: update API documentation
chore: update dependencies

Types:

feat: New feature (MINOR version bump)
fix: Bug fix (PATCH version bump)
docs: Documentation only changes
style: Changes that do not affect the meaning of the code
refactor: Code change that neither fixes a bug nor adds a feature
perf: Code change that improves performance
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools

Breaking Changes: Add BREAKING CHANGE: in the commit footer to trigger a MAJOR version bump.

Tech Stack

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

License

MIT

Deploy Server

HTTP connection URL

security – no known vulnerabilities

license - permissive license

quality - confirmed to work

How are these scores calculated?

hybrid server

The server is able to function both locally and remotely, depending on the configuration or use case.

Tools

A hub server that connects to and manages other MCP (Model Context Protocol) servers.

Related MCP Servers

MCP Server
la-rebelion
-
security
A
license
-
quality
MCP Server simplifies the implementation of the Model Context Protocol by providing a user-friendly API to create custom tools and manage server workflows efficiently.
Last updated -
4
4
MIT License
MCP Server
agentico-dev
-
security
A
license
-
quality
MCP Server provides a simpler API to interact with the Model Context Protocol by allowing users to define custom tools and services to streamline workflows and processes.
Last updated -
3
3
MIT License
MCP Proxy Server
adamwattis
A
security
A
license
A
quality
A central hub that aggregates multiple MCP resource servers into a single unified interface, enabling users to access tools and capabilities from multiple backend servers through one connection point.
Last updated -
1
158
MIT License
Resource Hub Server
adamwattis
-
security
F
license
-
quality
An MCP server that connects to the Resource Hub, allowing centralized configuration and management of tools and resources across different MCP environments.
Last updated -
3

View all related MCP servers

MCP Hub MCP Server