
Bot Bridge CC Helper
io.github.1019666077-bitPublished by GitHub account 1019666077-bitv0.1.0Updated Oct 24, 2026
Bridge a remote bot to a local Bot Bridge CC Helper: dispatch coding tasks and read progress.
Overview
Bridges a remote MCP bot to a local Bot Bridge CC Helper on Windows, letting an assistant queue coding jobs and read their progress and results.
- What you can do
- Check whether a local Helper install exists and where its job folders are
- Queue a coding job with an id, title and prompt into the Helper's inbox
- Read one job's state from the running or done folders
- List queued, running and finished jobs
- Cancel a running job by writing a stop control command
- When to use it
- Use it when you already run the Bot Bridge CC Helper desktop tray/daemon on Windows and want a remote assistant or bot to hand coding tasks to your local coding agent and follow their progress. Without that install it is not useful.
- Requirements
- Node.js 18 or newer, launched over stdio (for example via npx). A local Bot Bridge CC Helper install on Windows that owns the inbox, running, done and control folders. The optional CC_HELPER_HOME environment variable points at the Helper folder; it defaults to the user profile's cc-helper directory.
Installation
In SourceWeft
- Open Bot Bridge CC Helper in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
botbridge-cc-helper-mcp
An MCP stdio server that bridges a remote bot (any MCP client) to a local Bot Bridge CC Helper running on Windows. You dispatch a coding task into the Helper's inbox and read progress and results back out.
Independent product. This is not an Anthropic product and is not affiliated with, endorsed by, or sponsored by Anthropic. It talks to a local Bot Bridge CC Helper install that you run yourself.
Requirements
This package is a file bridge. It is useful only together with a local Bot Bridge CC Helper install — the desktop tray/daemon that actually owns the job folders and runs your local coding agent. Without that install every tool still answers, but reports that nothing is installed.
- Node.js >= 18
- A local Bot Bridge CC Helper install (Windows), which owns:
inbox\— one JSON file per queued jobrunning\— per-job progress while a job runsdone\— final state per jobcontrol\— cancellation commands
The Helper folder defaults to %USERPROFILE%\cc-helper and can be pointed
elsewhere with the CC_HELPER_HOME environment variable.
Install
Or run it without installing:
Usage
The server speaks MCP over stdio, so your MCP client launches it:
CC_HELPER_HOME is optional; omit it to use %USERPROFILE%\cc-helper.
Check the install from a terminal:
Tools
Environment variables
Source
The bridge ships byte-identical inside the
Bot Bridge CC Helper
VS Code extension as scripts/cc-helper-mcp.js, which is the source of truth.
npm run sync refreshes bin/botbridge-cc-helper-mcp.js from it; prepack
fails the build if the two ever drift apart.
License
MIT. See LICENSE.
Source: packages/botbridge-cc-helper-mcp/README.md at commit 8a65aef
Tools
0Version history
1- v0.1.0LatestOct 12, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts