Mcphub MCP Server

A hub server for mcp servers

Local serverstdioPython

What is the Mcphub MCP server?

A hub server for mcp servers. The mcphub mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

MCPHub makes it easy to manage and scale multiple MCP (Model Context Protocol) servers by organizing them into flexible Streamable HTTP (SSE) endpoints—supporting access to all servers, individual servers, or logical server groups.

Its toolset

Everything the assistant can do here goes through one of these:

  • Documentationdocs.mcphub.app
  • Hot — Swappable Config** - Add, remove, or update servers without downtime
  • Docker-Ready — Deploy instantly with containerized setup
  • Backend — Node.js, Express, TypeScript (ESM)
  • Frontend — React, Vite, Tailwind CSS
  • Storage — file-based mcp_settings.json by default; PostgreSQL via TypeORM with pgvector for Smart Routing
  • Auth — JWT + bcrypt for local accounts; bearer keys; built-in OAuth 2.0 server (@node-oauth/oauth2-server); optional Better Auth for GitHub/Google login
  • Protocol — Model Context Protocol SDK
  • Topic — Description
  • Configuration — 📖 See Configuration Guide for full options including OAuth, environment variables, and more

Adding it to your client

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

When to reach for it

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mcphub's toolset — Documentation, Hot, Docker-Ready and 7 more — is a fair guide to whether it matches your workflow. It is maintained by samanhappy; 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.

Caveats

  • 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.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mcphub.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcphub mcp server does with a few real requests.

Available tools

ToolWhat it does
Documentation[docs.mcphub.app](https://docs.mcphub.app/)
HotSwappable Config** - Add, remove, or update servers without downtime
Docker-ReadyDeploy instantly with containerized setup
BackendNode.js, Express, TypeScript (ESM)
FrontendReact, Vite, Tailwind CSS
Storagefile-based mcp_settings.json by default; PostgreSQL via TypeORM with pgvector for Smart Routing
AuthJWT + bcrypt for local accounts; bearer keys; built-in OAuth 2.0 server (@node-oauth/oauth2-server); optional Better Auth for GitHub/Google login
ProtocolModel Context Protocol SDK
TopicDescription
Configuration📖 See [Configuration Guide](https://docs.mcphub.app/configuration/mcp-settings) for full options including OAuth, environment variables, and more.

How to install the Mcphub MCP server

{
  "mcpServers": {
    "time": {
      "command": "npx",
      "args": ["-y", "time-mcp"]
    },
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

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

Example prompts to try

  • Use Mcphub to Documentation.
  • Use Mcphub to Hot.
  • Use Mcphub to Docker-Ready.

Frequently asked questions

It connects Mcphub to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (Documentation, Hot, Docker-Ready, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mcphub directly.