claude-bridge-mcp

# claude-bridge [](https://github.com/JosiahSiegel/claude-bridge/actions/workflows/test.yml) [](https://github.com/JosiahSiegel/claude-bridge) [](./LICENSE) An MCP server that lets host-side Claude Cowork dispatch work into **Claude Code running inside your devcontainer**, over stdio. Cowork launches the bridge with `docker exec -i`; the bridge shells to `claude -p` and returns a structured result. ## Install Inside the devcontainer: ```bash # from PyPI (once published — see CHANGELOG.md): pip install claude-bridge-mcp # or pin to the latest main branch: pip install "git+https://github.com/JosiahSiegel/claude-bridge.git@main" # or for development (editable + dev deps): git clone https://github.com/JosiahSiegel/claude-bridge.git cd claude-bridge pip install -e ".[dev]" ``` > **Note on names**: the PyPI distribution is `claude-bridge-mcp` (the > bare `claude-bridge` name was already taken by an unrelated HTTP > gateway). The Python import (`import claude_bridge`), the CLI > (`claude-bridge`), and the MCP server name (`claude-bridge`) are > unchanged — only the `pip install` argument differs. A reference Dockerfile and `devcontainer.json` for downstream projects live in [`examples/devcontainer/`](./examples/devcontainer/). ## Quickstart Three things have to be true: the bridge installed in the container, its absolute path in the Claude Desktop config on the host, and Claude Desktop fully restarted. **1. Install in the container.** ```bash pip install claude-bridge-mcp which claude-bridge # copy this path — you'll paste it in step 2 ``` **2. Register with Claude Desktop on the host.** Open via `Settings → Developer → Edit Config`, or edit the file directly: * macOS: `~/Library/Application Support/Claude/claude_des…