Mcp-hub MCP Server

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

Local serverstdiostreamable-http

What is the Mcp-hub MCP Server?

Mcp-hub is an MCP integration. Many stdio MCP servers from one container, published over HTTPS with OAuth 2.1 for any MCP client.

Packages and local setup

The published npm package is @ni-c/mcp-hub, version 0.11.6. Its declared MCP transport is stdio.

The package declares CONFIG_PATH: 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: 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: Tool snapshots of sleeping servers (default .mcp-hub/tool-cache.json beside the config); LOG_FILE: Mirror the hub's log lines into this file; stdout carries the protocol, so logging goes to stderr otherwise.

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

The published oci package is ghcr.io/ni-c/mcp-hub:0.11.6. Its declared MCP transport is streamable-http.

The package declares EXTERNAL_URL (required): Public base URL exactly as clients see it, e.g. https://mcp.example.net (no path); PASSWORD_HASH (required): bcrypt hash of the OAuth login password (htpasswd -bnBC 10 "" 'pw' | tr -d ':\n'); TRUSTED_PROXIES: Comma-separated IPs/CIDRs of the reverse proxy allowed to set X-Forwarded- headers; CLIENT_REGISTRATION: Which mechanisms a client may use to obtain a client_id: cimd (Client ID Metadata Documents), dcr (RFC 7591 dynamic registration), or both; CIMD_ALLOWED_ORIGINS: Comma-separated https origins whose client ID metadata documents are accepted, e.g. https://chatgpt.com; unset admits every https origin; PORT: Listen port inside the container.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.11.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
CONFIG_PATHPath to the mcp.json listing the servers to expose, in Claude Code's mcpServers format (default mcp.json in the working directory)Optional
IDLE_TIMEOUT_MINUTESMinutes of inactivity before a server is put to sleep; 0 starts every server at launch and keeps it running (default 60)Optional
TOOL_CACHE_PATHTool snapshots of sleeping servers (default .mcp-hub/tool-cache.json beside the config)Optional
LOG_FILEMirror the hub's log lines into this file; stdout carries the protocol, so logging goes to stderr otherwiseOptional