McpHub

McpHub sits between your AI editors and all your MCP servers.

Your agents see 3 tools instead of hundreds , every call goes through the same security guards ,

and your servers run once, sandboxed , shared by Cursor, Claude, Windsurf and VS Code.

Install · Connect your editor · How it works · Code mode · Security · Dashboard · Library · Linux and sync · Configuration · FAQ

---

✨ At a glance

-99.9% tokens spent on tool definitions 1,054,593 → 918 on a 928-tool setup 1 process for every editor servers start once, survive editor restarts 8 layers of security Keychain, pinning, sandbox, audit... 0 runtime dependencies a single signed Rust binary

---

🚀 Install in one line

curl -fsSL https://raw.githubusercontent.com/Soflutionltd/McpHub/main/get.sh | bash

The script downloads the latest binary for your machine (signed universal binary on macOS, x64 or arm64 on Linux), verifies its SHA-256 checksum and installs it to ~/.local/bin/McpHub. Then:

McpHub dashboard  # Library tab: add servers from the official MCP Registry (or McpHub add)

McpHub generate # index every tool once McpHub install # start the daemon at login (LaunchAgent on macOS, systemd --user on Linux)

Manual download

1. Download McpHub-macos-universal.tar.gz and its checksum.
2. shasum -a 256 -c McpHub-macos-universal.tar.gz.sha256
3. tar -xzf McpHub-macos-universal.tar.gz && install -m 755 McpHub ~/.local/bin/McpHub
4. Downloaded through a browser? Clear the quarantine flag: xattr -d com.apple.quarantine ~/.local/bin/McpHub

Linux (amd64, arm64) and Windows (amd64) archives are attached to every release too. On Linux the sandbox uses bubblewrap and secrets live in ~/.McpHub/secrets.env (mode 600, hidden from sandboxed servers), see Linux servers and sync. Windows has no sandbox.

Build from source

git clone https://github.com/Soflutionltd/McpHub.git

cd McpHub make install # cargo build --release, install, sign

make install signs with your Developer ID certificate when one is present, so macOS keeps its permissions from one version to the next. Linux and Windows build from source (cargo build --release); the macOS sandbox and Keychain features are macOS only.

🔄 Updates

Once the daemon runs (McpHub install), McpHub keeps itself up to date. Editors connected by URL (Cursor, Claude Code, VS Code, Windsurf) need nothing: they talk to the updated daemon.

• Signed. Every release publishes latest.json (version and SHA-256 of each file) signed with minisign; the public key is compiled into McpHub. On macOS the new binary must also carry Soflution's Developer ID signature. Anything else is refused.
• Gradual. A new version reaches 10% of installations on day one, everyone after 24 hours. The daemon checks at start-up, then every 6 hours. The only request is the download from GitHub: no telemetry, the rollout bucket is drawn from a random local id that never leaves your machine.
• Never in the middle of a call. The new binary is installed next to the old one; each daemon switches over as soon as no request is in flight (editors reconnect by themselves). If the new version fails to start three times, the previous one is restored and that version is skipped.
• Your choice. "settings": { "autoUpdate": false } turns it off; McpHub update installs the latest release right away, McpHub update --check only reports it. Development builds and named instances never update themselves (the main instance updates the shared binary).
• Claude Desktop extension. mcphub.mcpb uses the installed McpHub when there is one, so it follows the same updates; otherwise it runs the binary it ships with.
• Windows. The binary is replaced in place and used from the next session start.

---

🔌 Connect your editor

The daemon listens on http://127.0.0.1:24680. Your token is in ~/.McpHub/auth-token.

Cursor , ~/.cursor/mcp.json

{

"mcpServers": { "McpHub": { "url": "http://127.0.0.1:24680/mcp", "headers": { "Authorization": "Bearer " } } } }

Claude Code

claude mcp add --transport http mcphub http://127.0.0.1:24680/mcp \

--header "Authorization: Bearer $(cat ~/.McpHub/auth-token)"

Claude Desktop , claude_desktop_config.json

{

"mcpServers": { "McpHub": { "command": "/Users/you/.local/bin/McpHub", "args": ["stdio"] } } }

VS Code , .vscode/mcp.json

{

"servers": { "mcphub": { "type": "http", "url": "http://127.0.0.1:24680/mcp", "headers": { "Authorization": "Bearer " } } } }

Windsurf and other SSE clients

Use http://127.0.0.1:24680/sse with the same Authorization header.

One profile per client. Give each editor its own view: http://127.0.0.1:24680/mcp/cursor only shows what the cursor profile allows (see Profiles).

Project-aware client (optional)

client/ is a small Node MCP server that sits between your editor and the daemon. It talks to the running daemon (SSE, token from ~/.McpHub/auth-token) and falls back to McpHub stdio. It exposes six tools:

• mcphub_bootstrap: call once per conversation. Resolves the project from the workspace, returns its aliases and allowed servers, and recalls compact MemoryPilot context, also for folders without a project entry.
• mcphub_search, mcphub_call: same as the daemon, plus suggestions on a misspelled tool or server, and the input schema on argument errors.
• mcphub_batch: up to 20 independent calls in one round-trip.
• mcphub_status, mcphub_savings: server health and an honest context-size comparison.

Per-project policy lives in ~/.McpHub/projects.json (or the path in MCPHUB_PROJECTS), see client/projects.example.json. For a workspace listed there, only its allowedServers are reachable, and a call aimed at another Supabase project, App Store app or Cloudflare project is refused. Without the file there is no policy; an unreadable file is an error, never silently ignored.

Each release ships the client as a single file, mcphub-client.mjs, which the daemon keeps up to date in ~/.McpHub/client/ (Node 20 or later, no npm install). Editors pick up a new version the next time they start the server:

{

"mcpServers": { "McpHub": { "command": "node", "args": ["/Users/you/.McpHub/client/mcphub-client.mjs"] } } }

From a clone instead: cd client && npm ci, then point args at /path/to/McpHub/client/index.js.

npm test runs smoke tests against the local daemon (MemoryPilot and supabase configured), with a throwaway project file.

Working on client accounts

Connecting to a client's Stripe (or Supabase, Cloudflare…) should not log you out of your own, and your own agent should never reach theirs by mistake. Two levels, from light to strict:

1. Client-owned servers (same McpHub). Add the client's server under its own name (stripe-acme, with its own OAuth token or restricted key, since tokens are stored per server name) and list it in the client project's ownedServers:

"acme": {

"workspaces": ["/Users/you/Clients/Acme"], "aliases": { "product": "Acme" }, "allowedServers": ["MemoryPilot", "context7"], "ownedServers": ["stripe-acme"] }

An owned server only answers, appears in mcphub_search and in mcphub_status when working_dir is inside that client's workspace; the project argument alone is not enough. A server owned by two projects is a start-up error. This guard lives in the Node client: an editor connected straight to the daemon still sees every server, so give it a profile with "excludeServers": ["*-acme"].

2. A separate instance (nothing shared). For clients who require it, run a second McpHub with its own folder, port, Keychain service, auth token and LaunchAgent:

export MCPHUB_INSTANCE=acme MCPHUB_PORT=24690

McpHub add # writes ~/.McpHub-acme/config.json McpHub oauth login stripe # token stored under Keychain service McpHub-acme McpHub install # Launc