
A hub server that connects to and manages other MCP (Model Context Protocol) servers.
A hub server that connects to and manages other MCP (Model Context Protocol) servers.
·
A hub server that connects to and manages other MCP (Model Context Protocol) servers.
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.
Add this to your mcp.json:
{
"mcpServers": {
"other-tools": {
"command": "npx",
"args": [
"-y",
"mcp-hub-mcp",
"--config-path",
"/Users/username/mcp.json"
]
}
}
}# Clone repository
git clone <repository-url>
cd mcp-hub-mcp
# Install dependencies
npm install
# or
yarn install
# or
pnpm installnpm run build
# or
yarn build
# or
pnpm buildnpm start
# or
yarn start
# or
pnpm startnpm run dev
# or
yarn dev
# or
pnpm devThe 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:
MCP_CONFIG_PATH environment variable to the configuration file path--config-path option to specify the configuration file pathmcp-config.json file in the current directoryConfiguration 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"]
}
}
}The MCP-Hub-MCP server provides the following tools:
list-all-toolsReturns a list of tools from all connected servers.
{
"name": "list-all-tools",
"arguments": {}
}call-toolCalls 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"
}
}
}find-toolsFind 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"]
}
}
]
}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 dependenciesTypes:
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 toolsBreaking Changes:
Add BREAKING CHANGE: in the commit footer to trigger a MAJOR version bump.
MIT
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add other-tools -- npx -y mcp-hub-mcp --config-path /Users/username/mcp.json{
"mcpServers": {
"other-tools": {
"args": [
"-y",
"mcp-hub-mcp",
"--config-path",
"/Users/username/mcp.json"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"other-tools","args":["-y","mcp-hub-mcp","--config-path","/Users/username/mcp.json"],"command":"npx"}'[mcp_servers.other-tools]
command = "npx"
args = ["-y", "mcp-hub-mcp", "--config-path", "/Users/username/mcp.json"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/mcp-hub-mcp-server to learn what the "MCP-Hub-MCP Server" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
| Name | What it does |
|---|---|
list-all-tools | 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 y |
call-tool | Call a specific tool from a specific server. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName |
find-tools | 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. |
get-tool | 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 |
list-all-tools-in-server | List ALL tools from a specific MCP server (returns name and description only) |
find-tools-in-server | Find tools matching a pattern in a specific MCP server (returns name and description only) |
list-servers | List all connected MCP servers |
Read live from the server on September 26, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/mcp-hub-mcp-server)Nothing comparable is listed yet.
v1.3.1Release notesv1.3.0Release notesv1.2.0Release notesv1.1.1Release notesv1.1.0Release notesv1.0.3Release notesv1.0.2Release notesv1.0.1Release notesv1.0.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "mcp-hub-mcp-server" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.