← Back to directory

MCPHub

Community

Unified hub for centrally managing multiple MCP servers

GitHub source repository ↗

★ 2.3k Stars Category · Other Very popular Source revision 3548ca141b30

42FMRS · D

Reliability

7/20

Security and permissions

8/20

Maintenance

10/20

Documentation

9/20

Setup experience

8/20

MCPHub is a feature-rich MCP gateway offering powerful centralized management and routing capabilities. It suits teams that need to manage multiple MCP servers but requires attention to security configuration and resource consumption.

Read the FMRS scoring method →

MCPHub is a unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies. It offers a centralized dashboard, flexible routing, granular control over tool/prompt/resource visibility per group, AI-powered tool discovery via vector semantic search, MCP Apps proxy, tool result compression, hot-swappable configuration, OAuth 2.0 support, social login, database mode with PostgreSQL, and Docker-ready deployment.

Tools

The tool list has not been reviewed yet.

Setup

Create an mcp_settings.json file with your MCP server configurations.
Run with Docker: docker run -p 3000:3000 -v ./mcp_settings.json:/app/mcp_settings.json -v ./data:/app/data samanhappy/mcphub.
Access http://localhost:3000, log in with username 'admin'; on first launch, a random password is generated and printed to logs, or you can pre-set it via environment variable ADMIN_PASSWORD.
Connect AI clients to endpoints: http://localhost:3000/mcp (all servers), /mcp/{group} (group), /mcp/{server} (specific server), /mcp/$smart (smart routing).

Fit and risk

Best for

Development teams needing centralized management of multiple MCP servers
Organizations exposing various MCP servers to AI clients via a unified API
Production deployments requiring high availability and scalability
Solo developers wanting to quickly experiment with various MCP servers

Not for

Simple scenarios requiring only a single MCP server
Users with strict customization needs for a specific MCP server
Environments where running without authentication is unacceptable (high security requirements)

Required permissions

Access to MCP server configuration files and local data directory
Ability to execute commands like npx and uvx to start MCP servers
Network access to communicate with MCP servers
Optional: PostgreSQL database connection for database mode

Risks and side effects

MCP endpoints require authentication by default; unauthenticated access may expose servers
Hot-swappable configuration could lead to configuration errors causing service unavailability
Running many MCP servers may consume significant system resources
Admin password and API keys need careful management

Troubleshooting

Common issues: 1. Ensure mcp_settings.json is well-formed and server commands are executable. 2. Check that Docker volumes for config and data are correctly mounted. 3. Confirm port 3000 is not in use. 4. If unable to log in, check generated password in logs or set ADMIN_PASSWORD. 5. If MCP endpoints are inaccessible, review authentication settings.

Use cases

Manage and access multiple MCP servers under one unified endpoint

Route per group or individual server, controlling visibility of tools/prompts/resources

Leverage smart routing for AI-powered tool discovery

Secure authentication via OAuth 2.0 and social login

Rapid deployment in Docker environments

Supported clients

Claude DesktopFull support

CursorFull support

Related MCP servers

Compare with other MCP servers