MCP Hub MCP Server

A manager server for MCP servers that handles process management and tool routing

Local serverstdio

What is the MCP Hub MCP server?

MCP Hub MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Hub directly instead of describing what you should do. A manager server for MCP servers that handles process management and tool routing.

What you get

MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces:

  • Unified MCP Server Endpoint — (/mcp):
  • Single endpoint for ALL MCP clients to connect to
  • Access capabilities from all managed servers through one connection
  • Automatic namespacing prevents conflicts between servers
  • Real-time capability updates when servers change
  • Simplified client configuration - just one endpoint instead of many

What the assistant can call

Once MCP Hub is connected, these are the calls the assistant has available:

  • Components — The Components tool exposed by this server

Configuration and credentials

You will need 8 environment variables: API_KEY, API_TOKEN, DB_URL, DB_PASSWORD, DBUS_SESSION_BUS_ADDRESS, MY_TOKEN, MCP_HUB_ENV, PERPLEXITY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

mcp-hub on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Hub's toolset — Components — is a fair guide to whether it matches your workflow. It is maintained by ravitemer; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp hub mcp server does with a few real requests.

Available tools

ToolWhat it does
ComponentsThe Components tool exposed by this server.

How to install the MCP Hub MCP server

{
    "mcpServers" : {
        "Hub": {
            "url" : "http://localhost:37373/mcp"  
        }
    }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
API_KEYCredential the server authenticates with.Yes
API_TOKENCredential the server authenticates with.Yes
DB_URLEndpoint or connection string the server talks to.Yes
DB_PASSWORDConfiguration value read at startup.Optional
DBUS_SESSION_BUS_ADDRESSConfiguration value read at startup.Optional
MY_TOKENCredential the server authenticates with.Yes
MCP_HUB_ENVConfiguration value read at startup.Optional
PERPLEXITY_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Hub to Components.

Frequently asked questions

It connects MCP Hub to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Components) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Hub directly.