MCP-Hub MCP

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.

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

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

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

# Clone repository git clone <repository-url> cd mcp-hub-mcp # Install dependencies npm install # or yarn install # or pnpm install

npm run build # or yarn build # or pnpm build

npm start # or yarn start # or pnpm start

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 theMCP_CONFIG_PATHenvironment variable to the configuration file path
- Command line argument: Use the--config-pathoption to specify the configuration file path
- Default path: Usemcp-config.jsonfile in the current directory

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

{ "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:

Returns a list of tools from all connected servers.

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

- 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" } } }

Find tools matching a regex pattern across all connected servers (grep-like functionality).

- pattern: Regex pattern to search for in tool names and descriptions
- searchIn: 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 } }

- "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"

{ "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 followsConventional Commitsfor automatic versioning and CHANGELOG generation.

Connects AI agents to the SS&C Next Generation REST API to automate business processes.