What runtime and dependencies are required?
Node.js v20+ and npm are required. The underlying MCP servers you want to manage must be installed and accessible on your system.
MCP Server Hub / Gateway
@bsmi021
基本信息
关于 MCP Server Hub / Gateway
This project provides a central gateway to manage multiple MCP (Model Context Protocol) servers, preventing the need to configure and run duplicate server processes for each LLM client (like Cline, Cursor, etc.). Connect your LLM client to the single gateway-client endpoint provi
MCP Server Hub / Gateway 配置
MCP Server Hub / Gateway 工具
工具列表暂未提供
当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。
工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。
概览
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.
常见问题
How does dynamic configuration reloading work?
The gateway server watches `dist/mcp_hub_config.json` for file changes. When the file is saved, changes to `mcpServers`, `hubTools`, and other sections are automatically applied without restarting the gateway.
What naming restrictions apply to server and tool keys?
Server IDs and hub tool keys in `mcp_hub_config.json` must only contain the characters `a-zA-Z0-9_-`.
How does my LLM client connect to the gateway?
Configure your LLM client with a single MCP server entry called `gateway-client`. It uses `node` to run `dist/client/client.js` and connects to the already running gateway server via WebSocket.
Can I refresh the tool list without restarting the client?
The Gateway Client periodically polls the Gateway Server for tool list updates (every 5 minutes by default, configurable via `CLIENT_TOOL_REFRESH_INTERVAL_MS`). However, this does not work in Claude Desktop; a client restart is needed there.
其他 分类下的更多 MCP 服务器
Klarix Intelligence Engine
KlarixB2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
Codelf
unbugA search tool helps dev to solve the naming things problem.
14.2K
Volley.sh
VolleyA good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Glasswarp
GlasswarpSee and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.
ICSS
chokcoco不止于 CSS
20.7K
评论