Containerize the local MCP sidecar, not the whole compare-first product.
This Docker entry wraps the local Prompt Switchboard MCP sidecar so builder-facing flows can launch it from a container. The browser extension still runs on the host machine, and Prompt Switchboard does not turn into a hosted compare service here.
What it is
- a containerized wrapper around
npm run mcp:server - a local
stdioMCP surface for Codex / Claude Code style clients - a published host port for the loopback bridge when you run
-p 48123:48123
What it is not
- not a hosted compare service
- not a public HTTP API
- not proof of a Glama, Chrome Web Store, or registry listing
Build and run
docker build -t prompt-switchboard-mcp .
docker run --rm -i -p 48123:48123 prompt-switchboard-mcp server
Use docker run --rm prompt-switchboard-mcp doctor for the repo-owned doctor
envelope, and check http://127.0.0.1:48123/health for runtime bridge
readiness once the container is up.
Full operator notes live in docker/README.md. The short truthful split is:
containerized sidecar now, external listing later.
Current public Glama pages verify a server catalog and connector surfaces, but this repo does not claim a Prompt Switchboard listing there yet.