mcp s-hub

Explore MCP Servers and Clients.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio tmstack-mcp-servers-hub node server.js \
  --env PORT="8080" \
  --env MCP_API_HOST="http://localhost:8080" \
  --env MCP_LOG_LEVEL="info"

How to use

The tmstack-mcp-servers-hub is a centralized MCP hub that aggregates and exposes a collection of MCP servers and clients, enabling you to discover, route to, and orchestrate MCP-enabled tooling from a single entrypoint. Once running, the hub acts as a gateway that can enumerate available MCP servers, proxy commands, and route context between clients and servers within your environment. Use cases include exploring added MCP servers, coordinating cross-server workflows, and debugging MCP interactions across multiple components. To get started, run the hub and connect MCP clients to it using the hub's URL and port. The hub will list registered MCP servers and expose a unified interface for issuing MCP commands and retrieving contextual results.

How to install

Prerequisites:

Node.js 14+ installed on your system
Git (optional, for cloning the repository)

Steps:

Clone the repository:

git clone https://github.com/your-org/tmstack-mcp-servers-hub.git
cd tmstack-mcp-servers-hub

Install dependencies:

npm install

Configure environment (if you need custom ports or hosts):

export PORT=8080
export MCP_API_HOST=http://localhost:8080

Run the hub:

node server.js

(Optional) Run as a background service or using a process manager like PM2:

pm install -g pm2
pm2 start server.js --name tmstack-mcp-servers-hub

Notes:

Ensure the designated port (default 8080) is open in your firewall.
If you integrate with other MCP servers, add them to the hub's configuration or startup script as additional mcpServers entries.

Additional notes

Tips and caveats:

The hub relies on a registry of MCP servers. If a connected server goes offline, the hub should automatically reflect its unavailable status but may retry connections based on your configuration.
Common environment variables you may need: PORT, MCP_API_HOST, MCP_LOG_LEVEL, and any authentication tokens required by downstream MCP servers.
If you modify the hub to include TLS, consider setting up proper certificates and updating the connection URLs in your clients.
When debugging, set MCP_LOG_LEVEL to debug to get more verbose output for tracing MCP context flows.