MCP Server Hub / Gateway

What is MCP Server Hub / Gateway?

MCP Server Hub / Gateway is a central gateway that manages multiple MCP (Model Context Protocol) servers and exposes hub-native tools through a single endpoint. It eliminates the need to configure duplicate server processes for each LLM client (e.g., Cline, Cursor) and supports dynamic configuration reloading without restarting the gateway.

How to use MCP Server Hub / Gateway?

Install Node.js v20+, clone the repo, run npm install then npm run build, edit mcp_hub_config.json in the project root. Start the gateway server with npm start. Configure your LLM client to use the gateway-client MCP server with command: "node" and args: ["<absolute-path-to-project>/dist/client/client.js"].

Key features of MCP Server Hub / Gateway

• Centralized management of multiple MCP servers and hub-native tools.
• Dynamic configuration reloading without restarting the gateway.
• Namespaced tool exposure (serverId__toolName, hub__toolName).
• WebSocket-based communication between Gateway Client and Server.
• Configurable internal services that react to configuration changes.
• Supports optional SSE interface and configurable log levels.

Use cases of MCP Server Hub / Gateway

• Replace separate MCP server entries for each LLM client with a single gateway.
• Dynamically add, remove, or update MCP servers and hub tools at runtime.
• Expose custom hub-native tools alongside managed server tools through one interface.
• Manage server lifecycle (start, stop, restart) centrally with auto‑restart options.