mcp-hub

Name: mcp-hub
Author: ni-c

by ni-cversion 0.12.0i★ –iRuns on your computer

Registry nameio.github.ni-c/mcp-hub

Install

Overview

Description from the maker (original English)

Many stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 340/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio, Streamable HTTP
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CONFIG_PATH, IDLE_TIMEOUT_MINUTES, TOOL_CACHE_PATH, LOG_FILE

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "hub": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/mcp-hub",
        "--stdio"
      ],
      "env": {
        "CONFIG_PATH": "your-value",
        "IDLE_TIMEOUT_MINUTES": "your-value",
        "TOOL_CACHE_PATH": "your-value",
        "LOG_FILE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add hub --env CONFIG_PATH=your-value --env IDLE_TIMEOUT_MINUTES=your-value --env TOOL_CACHE_PATH=your-value --env LOG_FILE=your-value -- npx -y @ni-c/mcp-hub --stdio

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "hub": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/mcp-hub",
        "--stdio"
      ],
      "env": {
        "CONFIG_PATH": "your-value",
        "IDLE_TIMEOUT_MINUTES": "your-value",
        "TOOL_CACHE_PATH": "your-value",
        "LOG_FILE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "hub": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/mcp-hub",
        "--stdio"
      ],
      "env": {
        "CONFIG_PATH": "your-value",
        "IDLE_TIMEOUT_MINUTES": "your-value",
        "TOOL_CACHE_PATH": "your-value",
        "LOG_FILE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CONFIG_PATH env
Path to the mcp.json listing the servers to expose, in Claude Code's mcpServers format (default mcp.json in the working directory)
IDLE_TIMEOUT_MINUTES env
Minutes of inactivity before a server is put to sleep; 0 starts every server at launch and keeps it running (default 60)
TOOL_CACHE_PATH env
Tool snapshots of sleeping servers (default .mcp-hub/tool-cache.json beside the config)
LOG_FILE env
Mirror the hub's log lines into this file; stdout carries the protocol, so logging goes to stderr otherwise

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ni-c, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 5558 servers in this category
Published to the registry more recently than 77% of the other 5558 servers in this category
Basic checks equal to or better than 100% of the other 5558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is mcp-hub safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.12.0) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 5 days ago

Computer or cloud

Install

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 17 days ago

Runs on your computer

Install

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-hub

A dual-era Model Context Protocol (MCP) gateway: it serves many stdio MCP servers from one container, published over HTTPS, and speaks both MCP revisions on every endpoint — 2026-07-28 and 2025-11-25. The client picks, and cannot tell which one it is on from the answers. On the 2026 revision that includes elicitation — a child server's question reaches the person at the far end instead of dying at the gateway (how) — and subscriptions: the hub serves subscriptions/listen to its clients and subscribes to its children on whichever revision _they_ speak, so a server that has never heard of it still reaches a client that speaks nothing else (how).

Lets MCP clients that cannot spawn a local process — ChatGPT connectors, Claude on the Web and in Code, Mistral Le Chat, Cursor, LibreChat and any other Streamable-HTTP client — reach every server behind it, with a built-in OAuth 2.1 login protected by a single password, plus long-lived API tokens for clients that cannot do OAuth (OpenAI Responses API, xAI API, Gemini API). Per-client recipes: client compatibility.

Want to poke at it first? demo/ is a throwaway hub with three fake servers — docker compose up -d, then point the MCP Inspector or MCPJam at it. Nothing to configure, nothing to clean up but a volume.

Why

Wrapping each stdio MCP server in its own auth-proxy container costs a full image, an OAuth stack, a hostname and a compose stack _per server_. mcp-hub replaces N containers with one process:

Config is exactly Claude Code's `mcpServers` format — copy entries 1:1.
Path-based routing: https://host/paperless, https://host/homeassistant, …
`/hub` aggregate: register a _single_ connector and reach every server through 6 meta-tools (list_servers, list_tools, get_tool_schema, call_tool, wake_server, sleep_server) without flooding the model context with N×tools schemas.
Per-server tool filtering: allowTools / denyTools on any server decide which of its tools the hub exposes — exact names or list_* prefixes. A filtered tool is hidden from tools/list _and_ refused if a client calls it anyway, before the server is even woken, so a client holding a stale schema cannot reach it.
Also without HTTP: mcp-hub --stdio serves that same aggregate on stdin/stdout for clients that can only spawn a local process (Claude Desktop, Codex, …) — same mcp.json, no TLS, no reverse proxy, no login. Auth exists for the network endpoints; over stdio the trust boundary is the local user.
On-demand lifecycle: stdio and docker servers start when used and sleep after 60 idle minutes, answering initialize/tools/list from a persistent snapshot meanwhile — a dozen servers cost only the memory of the ones in use. keepAlive: true exempts a server, IDLE_TIMEOUT_MINUTES=0 the hub.
Servers that stay locked until you say so: "unlock": true on a shell, a mailbox or your DNS, and a model that calls it gets a link instead of a result. You unlock it on the hub's page with your password (and code) for one call or 15 minutes to four hours, for the connection that asked and nobody else. Clients that open pages themselves get the link as a URL elicitation, every other client as text, and a whole-locked server is put to sleep when its last unlock ends.
Optional two-factor login: TWO_FACTOR=totp adds a code from any authenticator app to the password on the OAuth login. Codes work once, wrong ones pause further attempts, and switching it on retires every token that a password alone had issued. mcp-hub-admin totp init draws the QR code in the terminal.
CIMD-first OAuth 2.1: clients identify themselves with a Client ID Metadata Document — the registration-free path the MCP spec now prefers — including private_key_jwt against the keys in their own document (metadata-document clients only). RFC 7591 dynamic registration stays advertised beside it for older clients, mcp-hub-admin clients add issues credentials by hand for anything that can do neither, and CLIENT_REGISTRATION turns either mechanism off.
OAuth outwards, too: a remote server that speaks OAuth gets an oauth block instead of a static header. The hub registers itself — with credentials the upstream issued, via RFC 7591, or with its own client metadata document — then obtains and refreshes the token. client_credentials upstreams need no attention at all; where a person must sign in, mcp-hub-admin upstream login prints one URL. An upstream that needs re-authorizing shows up as one server unauthorized, not as a confusing 401 in your client.
Supervision: children are pinged and restarted with exponential backoff when they die. A down server answers 503, not silence; a crash-looping server nobody uses is parked instead of restarted forever.
Hot reload: edits to mcp.json start/stop/restart only the affected servers.
Stateless Streamable HTTP: no session state, so claude.ai's reconnect-without-DELETE behaviour cannot leak processes or memory.
Dual-era: every endpoint — /hub, / /mcp and --stdio — answers MCP 2026-07-28 and 2025-11-25 alike; the client picks and cannot tell from the answers which it got. On the 2026 revision that includes elicitation: a server asking the user something returns the question rather than pushing it, so it reaches the person at the far end instead of dying at the gateway. The hub attributes it to the server that asked, strips what could lie about that, drops embedded sampling and roots requests, and seals the resumption state against the call it belongs to. `passthrough:

"off"` withdraws one server's right to ask; details.

Change notifications, in both eras: a client opens a subscriptions/listen stream and hears when a child's tools, prompts or resources change. The hub subscribes to each child the way that child understands — subscriptions/listen to a 2026 server, resources/subscribe to a 2025 one — so the era gap is the gateway's problem rather than either end's. The state is the open response, not a session table, so this costs the stateless design nothing. A sleeping server watches nothing and is told to re-read on waking; subscriptions: "off" withdraws one server's right to push; details.
Lightweight by design: one Node process, no database (state is one JSON file plus a signing key under /data), ten runtime dependencies, and multi-arch images — a stated project goal is to run comfortably on a single-board computer like a Raspberry Pi.

Servers to run behind it

The hub is server-agnostic — it serves any stdio MCP server whose entry fits Claude Code's mcpServers format, which is most of them. These nineteen are built and maintained alongside it, so their documentation carries the hub entry you need and their tool filters line up with the hub's own allowTools / denyTools:

Server	npm	What it reaches
audiobookshelf-mcp	`audiobookshelf-mcp`	Audiobookshelf — libraries, listening progress, collections and playlists
caldav-mcp	`@ni-c/caldav-mcp`	CalDAV — events, tasks and journal entries on any server that speaks it
calibreweb-mcp	`calibreweb-mcp`	Calibre-Web — read-only library access through the OPDS feed
carddav-mcp	`@ni-c/carddav-mcp`	CardDAV — contacts, groups and photos on any server that speaks it
freshrss-mcp	`@ni-c/freshrss-mcp`	FreshRSS — feeds, categories and articles as plain text, not stream ids
google-search-console-mcp	`@ni-c/google-search-console-mcp`	Google Search Console — properties, sitemaps, search analytics, URL inspection
healthchecks-mcp	`healthchecks-mcp`	Healthchecks — cron and uptime checks, and why one failed
hetzner-dns-mcp	`hetzner-dns-mcp`	Hetzner Cloud DNS — zones, record sets and BIND import/export
imap-mcp	`@ni-c/imap-mcp`	IMAP mailboxes — read, search, organise and draft mail; it cannot send
linkwarden-mcp	`linkwarden-mcp`	Linkwarden — bookmarks, collections and the article text it preserved

| mealie-mcp | @ni-c/mealie-mcp | Mealie — recip

Only the beginning is shown; read the rest in the repo

mcp-hub

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

mcp-hub

Why

Servers to run behind it