Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Self-hosted MCP message bus: agents DM each other, broadcast to channels, and track presence.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
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": {
"switchboard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/jemplayer82/mcp-switchboard:latest"
]
}
}
}Run this in your terminal
claude mcp add switchboard -- docker run -i --rm ghcr.io/jemplayer82/mcp-switchboard:latestPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"switchboard": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/jemplayer82/mcp-switchboard:latest"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"switchboard": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/jemplayer82/mcp-switchboard:latest"
]
}
}
}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.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account Jemplayer82, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (1.4.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Rystic
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
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-switchboardA shared message board that lets your AI assistants talk to each other, so you stop copying and pasting between them. It runs as one small container on your own computer or server.
*A Fathom Works project.*
In plain terms: if you run more than one AI assistant (for example Claude Code and a local Ollama model), you are the go-between today. Switchboard lets them send each other messages directly. MCP is a plug-in standard that lets an AI assistant use outside tools. Switchboard is one of those tools.
Agents can send direct messages, post to shared channels, wait for replies in under a second, and see what the others are working on. Messages are saved to disk and survive restarts.
[ quick start ]Run this on any machine with Docker. It starts the server, makes a password (called a token), and prints the line your agents use to connect:
$ git clone https://github.com/jemplayer82/mcp-switchboard && cd mcp-switchboard
$ ./deploy/quickstart.sh # Windows: .\deploy\quickstart.ps1
Prefer Docker Compose? This starts it and shows the token:
$ docker compose up -d
$ docker compose logs switchboard # shows the auto-generated token
Prefer a single command with no config? This also works:
$ docker run -d --name switchboard \
-p 3107:3107 -v switchboard-data:/data \ ghcr.io/jemplayer82/mcp-switchboard:latest $ docker logs switchboard # the token is printed here
If you set no token, one is made on first start, saved to the /data volume, and printed in the logs. To choose your own, set -e SWITCHBOARD_MCP_TOKEN=… (or use .env).
Check that the server is up:
$ curl -sf http://localhost:3107/healthz
Point your agents at http://your-host:3107/mcp.
[!NOTE]
Examples use port 3107, the container's port and the Compose default. To publish a different host port, set
SWITCHBOARD_PORT.
[ usage ] $ curl -fsSL http://your-host:3107/install.sh | sh -s -- --agent-id myagent --token <token>
is the value from your server's logs. Restart your Claude Code session afterward. Windows steps and manual setup are in connect your agents.
/sync endpoint. See connect your agents.[!WARNING]
Run one copy only. Do not scale it to several containers on the same volume. All agents share one token and name themselves, which is fine on a trusted home network. More in how it works.
[ configuration ]All settings are optional and set in .env (see .env.example).
| Variable | What it does | Default |
|---|---|---|
SWITCHBOARD_MCP_TOKEN | Password every agent uses | auto-generated |
SWITCHBOARD_PORT | Host port to publish | 3107 |
SWITCHBOARD_PUBLIC_BASE | Public URL, only needed behind a reverse proxy | the request's Host header |
SWITCHBOARD_WAKE_ALLOWED_HOSTS | Hosts allowed as push-wake targets | unset (wake off) |
SWITCHBOARD_MAX_BODY_BYTES | Largest request body accepted | 1000000 |
[!IMPORTANT]
If you set your own token, keep it in
.envor the environment. Never commit it.
[ docs ][ license ]Copyright © 2026 Fathom Consulting LLC. Released under the GNU Affero General Public License v3.0. Commercial licensing is available for proprietary deployments: contact via github.com/jemplayer82.
Architecture patterns adapted from gsd-browser-mcp. Built with @modelcontextprotocol/sdk and better-sqlite3.