Tunnels local stdio MCP servers to an mcp-switchboard hub over one outbound WebSocket
Until 2026-09-24 this record combined several servers published from one repository. The others now have records of their own: mcp-switchboard-hub. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-switchboard-client","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-switchboard-client The client half of [mcp-switchboard](https://github.com/AkosPapp/mcp-switchboard). It reads an `mcp.json`, spawns the local stdio MCP servers it describes, and opens a single **outbound** WebSocket to an `mcp-switchboard-hub`, multiplexing every server over that one connection. No inbound port is ever opened, so it works from behind NAT with nothing forwarded. The client speaks no MCP itself — it is a pipe, shuttling each server's stdin/stdout across the tunnel. All MCP logic lives in the hub. That is why its only dependency is `websockets`. ## Running ```sh uvx mcp-switchboard-client --hub-url wss://switchboard.example.com --token "$TOKEN" ``` or bootstrap `uvx`/`npx` first with the installer: ```sh curl -fsSL https://akospapp.github.io/mcp-switchboard/install.sh | sh -s -- \ --hub-url wss://switchboard.example.com --token "$TOKEN" ``` `mcp.json` uses the familiar shape, resolved from the current directory: ```json { "mcpServers": { "git": { "command": "uvx", "args": ["mcp-server-git", "--repository", "."] } } } ``` Settings can also come from `MCP_SWITCHBOARD_*` environment variables or a `.env` file (`HUB_URL`, `TUNNEL_TOKEN`, `LABEL`, `CONFIG`, …). Any value that starts with `/` and points at an existing regular file is read from that file, so a token can be passed as a path. `LABEL` defaults to the machine's hostname and is how the hub tags this machine's tools, so consumers can tell which host a tool lives on. See the [main README](../README.md) for the full picture.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.