MCP Hub MCP Server
References Imgur for image hosting in the documentation
Connects to and manages multiple Node.js-based MCP servers, allowing access to tools across different servers from a single hub
Enables connecting to other MCP servers through npm packages using npx commands
Supports installation and execution using pnpm package manager
Built with TypeScript to provide type-safe interaction with other MCP servers and their tools
Supports installation and execution using Yarn package manager
Integrates Zod for schema validation of configuration files and tool arguments
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Hub MCP Server list all available tools from my connected servers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 connects to and manages multiple MCP (Model Context Protocol) servers through a single interface. It helps prevent excessive context usage and pollution from infrequently used MCPs (e.g., Atlassian MCP, Playwright MCP) by allowing you to connect them only when needed. This reduces AI mistakes and improves performance by keeping the active tool set focused and manageable.
Related MCP server: MCP-Hub-MCP Server
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"
]
}
}
}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 installBuild
npm run build
# or
yarn build
# or
pnpm buildRun
npm start
# or
yarn start
# or
pnpm startDevelopment Mode
npm run dev
# or
yarn dev
# or
pnpm devConfiguration 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_PATHenvironment variable to the configuration file pathCommand line argument: Use the
--config-pathoption to specify the configuration file pathDefault path: Use
mcp-config.jsonfile 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 fromtoolName: Name of the tool to calltoolArgs: Arguments to pass to the tool
{
"name": "call-tool",
"arguments": {
"serverName": "filesystem",
"toolName": "readFile",
"toolArgs": {
"path": "/Users/username/Desktop/example.txt"
}
}
}3. find-tools
Find tools matching a regex pattern across all connected servers (grep-like functionality).
pattern: Regex pattern to search for in tool names and descriptionssearchIn: Where to search: "name", "description", or "both" (default: "both")caseSensitive: Whether the search should be case-sensitive (default: false)
{
"name": "find-tools",
"arguments": {
"pattern": "file",
"searchIn": "both",
"caseSensitive": false
}
}Example patterns:
"file"- Find all tools containing "file""^read"- Find all tools starting with "read""(read|write).*file"- Find tools for reading or writing files"config$"- Find tools ending with "config"
Example output:
{
"filesystem": [
{
"name": "readFile",
"description": "Read the contents of a file",
"inputSchema": {
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Path to the file to read"
}
},
"required": ["path"]
}
},
{
"name": "writeFile",
"description": "Write content to a file",
"inputSchema": {
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Path to the file to write"
},
"content": {
"type": "string",
"description": "Content to write to the file"
}
},
"required": ["path", "content"]
}
}
]
}Commit Message Convention
This project follows Conventional Commits for automatic versioning and CHANGELOG generation.
Format: <type>(<scope>): <description>
Examples:
feat: add new hub connection featurefix: resolve issue with server timeoutdocs: update API documentationchore: update dependencies
Types:
feat: New feature (MINOR version bump)fix: Bug fix (PATCH version bump)docs: Documentation only changesstyle: Changes that do not affect the meaning of the coderefactor: Code change that neither fixes a bug nor adds a featureperf: Code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools
Breaking Changes:
Add BREAKING CHANGE: in the commit footer to trigger a MAJOR version bump.
Other Links
License
MIT
Available Tools
7 toolscall-toolCall ToolA
Call a specific tool from a specific server. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName
Inputs: toolArgs (required), toolName (required), serverName (required).
find-toolsFind ToolsA
Use this tool to find best tools by searching with keywords or regex patterns. If you don't have a specific tool for a task, this is the best way to discover what tools are available.
Inputs: pattern (required), searchIn, caseSensitive.
find-tools-in-serverFind Tools in ServerB
Find tools matching a pattern in a specific MCP server (returns name and description only)
Inputs: pattern (required), serverName (required), searchIn, caseSensitive.
get-toolGet Tool SchemaA
Get complete schema for a specific tool from a specific server, including inputSchema. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName
Inputs: toolName (required), serverName (required).
list-all-toolsList All ToolsA
List ALL available tools from all connected servers. NOTE: For better performance, use find-tools with keywords first. Only use this when you need to see everything or if find-tools didn't find what you need
Inputs: no named parameters.
list-all-tools-in-serverList Tools in ServerA
List ALL tools from a specific MCP server (returns name and description only)
Inputs: serverName (required).
list-serversList ServersB
List all connected MCP servers
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Most tools are clearly distinct by scope (global vs per-server, discovery vs schema vs invocation). Minor overlap exists between list-all-tools and find-tools, but the descriptions explicitly guide usage.
All tool names follow a consistent kebab-case verb-noun pattern, with clear modifiers like -in-server to indicate scope. The naming is uniform and predictable.
Seven tools is well-scoped for a meta-server that manages other MCP servers. Each tool covers a distinct operation without redundancy or bloat.
The surface covers the full workflow: discover servers, list tools, search tools, inspect schemas, and call tools. No obvious dead ends or missing critical operations for the stated purpose.
Maintenance
Related MCP Connectors
MCP server for hub documentation, generated by doc2mcp.
Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.
Trust, freshness, policy, and discovery layer for public MCP servers.
The official MCP Server for the Mux API
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA 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.202MIT
- AlicenseBqualityDmaintenanceA hub server that connects to and manages other MCP servers, allowing users to bypass Cursor's 40-tool limit and reduce AI mistakes by hiding infrequently used tools.23MIT
- FlicenseNot gradedqualityNot gradedmaintenanceMCP Hub aggregates and proxies multiple Model Context Protocol servers into a unified Streamable HTTP interface. It allows users to combine diverse stdio, SSE, and HTTP-based servers while providing tool namespacing, health monitoring, and secure authentication.497 npm-
- AlicenseNot gradedqualityDmaintenanceMCP hub server that aggregates tools from multiple domain packages into a single globally-available interface.1MIT