Mcphub MCP Server

A zero-dependency MCP gateway. Connect multiple AI agents to multiple MCP servers through a single, centrally-managed stdio interface. No overhead

Remote serverstreamable-http

What is the Mcphub MCP server?

Mcphub MCP server exists for a simple reason — assistants are far more useful when they can act on Mcphub directly instead of describing what you should do. A zero-dependency MCP gateway. Connect multiple AI agents to multiple MCP servers through a single, centrally-managed stdio interface. No overhead, no bloat — just the Node.js stdlib. Secrets stay in the OS keychain, never in config files.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

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

  • Keychain — The Keychain tool exposed by this server
  • stdio — Spawns a subprocess and communicates via JSON-RPC 2.0 over stdin/stdout. Stderr from the child is logged with the server name as prefix. Process exit

Configuration and credentials

You will need one environment variable: GITHUB_PERSONAL_ACCESS_TOKEN. 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.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • 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 mcphub mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mcphub's toolset — Keychain, stdio — is a fair guide to whether it matches your workflow. It is maintained by pcandido; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
KeychainThe Keychain tool exposed by this server.
stdioSpawns a subprocess and communicates via JSON-RPC 2.0 over stdin/stdout. Stderr from the child is logged with the server name as prefix. Process exit kills pending requests and cleans up.

How to install the Mcphub MCP server

{
  "mcpServers": {
    "mcphub": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@pcandido/mcphub", "serve"]
    }
  }
}

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

Configuration

VariableDescriptionRequired
GITHUB_PERSONAL_ACCESS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Mcphub to Keychain.
  • Use Mcphub to stdio.

Frequently asked questions

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