mcp-server-hub-server

Overview

The MCP Server Hub provides a centralized gateway to manage multiple MCP servers, eliminating the need to configure and run duplicate server processes for each LLM client. It supports dynamic configuration reloading, allowing managed servers and hub tools to be updated without restarting the main gateway. The system consists of a Gateway Server that manages MCP server lifecycles and loads hub-native tools, and a Gateway Client that proxies connections from LLM clients to the gateway.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

• hub__example

  An example tool provided by the hub itself.

  Try:Use the hub example tool to demonstrate its functionalityTry:Run the example hub tool with some sample data

Note: Only one tool is explicitly documented in the configuration schema. The actual tool names and functionality for hub-native tools depend on user implementation in src/tools/. The server primarily acts as a gateway for other MCP servers, whos

Comparable tools

Installation

{
  "mcpServers": {
    "gateway-client": {
      "command": "node",
      "args": [
        "/path/to/mcp-server-hub-server/dist/client/client.js"
      ],
      "options": {
        "cwd": "/path/to/mcp-server-hub-server"
      }
    }
  }
}

FAQ

How do I add a new MCP server to the hub?

Add the server configuration to the 'mcpServers' section in mcp_hub_config.json, specifying the command, args, and other settings. The gateway will automatically start and manage it.

Can I update the configuration without restarting the gateway server?

Yes. The hub supports dynamic configuration reloading. Changes to dist/mcp_hub_config.json while the server is running will be automatically detected and applied.

Compare mcp-server-hub-server with