MCP Hub

What is MCP Hub?

A centralized hub server that consolidates multiple MCP servers into dedicated Streamable HTTP or SSE endpoints, each tailored to specific use scenarios. It is designed for developers who need to manage and route multiple MCP servers through a single entry point.

How to use MCP Hub?

Install dependencies with pnpm, run pnpm build, then start the API server with pnpm dev:api or the CLI server with mcp-hub --init. Configure MCP servers in backend/config/mcp_service.json and groups in backend/config/group.json. Access tools via group-specific endpoints like /:group/mcp.

Key features of MCP Hub

• Multi-server MCP integration with centralized management.
• Group-based routing with dedicated endpoints.
• Standalone CLI MCP server for tool aggregation.
• Support for both Streamable HTTP and SSE endpoints.
• Tool filtering and validation keys per group.
• Modular monorepo architecture with core, API, CLI packages.

Use cases of MCP Hub

• Consolidate multiple MCP servers into a single hub.
• Expose different groups of tools for different use scenarios.
• Use CLI server to aggregate tools for MCP clients like Claude Desktop.
• Manage MCP servers via web interface with authentication and monitoring.

FAQ from MCP Hub

What are the prerequisites for running MCP Hub?

Node.js 18+ and the pnpm package manager are required.

How do I configure MCP servers?

Create a mcp_service.json file in backend/config/ with server command, args, and environment variables.

How do I access tools via groups?

Use endpoints in the format /:group/mcp, for example curl http://localhost:8181/development/mcp/list_tools.

Does the web interface have authentication?

Yes, it uses JWT-based authentication. Default credentials are username admin and password admin (must be changed in production).

Can I use the CLI as a standalone MCP server?

Yes. Install globally with npm install -g @mcp-core/mcp-hub-cli or run directly, then configure it in your MCP client using the CLI binary and a config file.