mcp-hub
A curated list of awesome Model Context Protocol (MCP) servers.
claude mcp add --transport stdio lobstercare-mcp-hub node path/to/server.js \ --env LOG_LEVEL="info" \ --env MCP_HUB_CONFIG="Path to config or inline settings as required by the hub"
How to use
mcp-hub appears to be a central MCP hub that coordinates multiple MCP servers. With a hub like this, you can route requests to various underlying MCP servers, aggregate responses, and manage access control and logging from a single entry point. The hub typically exposes an MCP-compatible API or endpoints that you can query using your favorite MCP client or developer tooling. Once running, you can connect client applications to the hub to discover, authenticate, and issue MCP commands to the connected servers through the hub layer. This helps standardize interactions and reduces the need to manage each MCP server individually from the client side.
To use the hub effectively, first ensure it is running and accessible at its configured host and port. Then, use your MCP client to target the hub endpoint for common operations (e.g., listing available MCP services, performing file reads, database queries, or other contextual actions). The hub will route requests to the appropriate underlying server implementations, aggregate results, and return a unified response. Depending on the hub’s capabilities, you may also be able to register new MCP servers, configure access controls, and monitor activity through an integrated dashboard or API calls.
How to install
Prerequisites:
- Node.js (latest LTS) and npm installed on your system
- Access to the repository containing the mcp-hub source code
Install and run locally:
-
Clone the repository git clone https://github.com/lobstercare/mcp-hub.git cd mcp-hub
-
Install dependencies npm install
-
Configure environment (example) Create a .env file or export variables in your shell: export MCP_HUB_CONFIG=/path/to/config.json export LOG_LEVEL=info
-
Start the hub npm run start
or if a different start script is provided in package.json, use that command
-
Verify it is running curl http://localhost:PORT/health
Note: If your deployment uses Docker or another runtime, adapt the commands accordingly using the mcp_config guidance in this doc.
Additional notes
Tips and common considerations:
- Ensure network access between the hub and all registered MCP servers; firewalls and DNS resolutions can block communication.
- Review authentication and authorization settings to control which clients can access the hub and underlying MCP services.
- Check logs frequently during initial setup to catch misconfigurations in environment variables or server registrations.
- If you upgrade Node.js or dependencies, run npm install to refresh the lockfile and keep compatibility with MCP protocol expectations.
- Maintain a registry of connected MCP servers with version information to help diagnose compatibility issues when routing requests.