# Bot Bridge CC Helper [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/1019666077-bit/botbridge-cc-helper-vscode  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/bot-bridge-cc-helper

## Description
Bridge a remote bot to a local Bot Bridge CC Helper: dispatch coding tasks and read progress.

## Tools
Capabilities this server exposes over MCP:

- **cc_helper_status** — Is the Helper installed, and how many jobs are queued/running/done.
- **cc_helper_dispatch** — Write one job JSON into `inbox\`. Returns the task id.
- **cc_helper_task_status** — Read `running\<id>\status.json` + `progress.md`, or `done\<id>\status.json`.
- **cc_helper_list_tasks** — List queued, running and finished tasks.
- **cc_helper_stop** — Write `stop` into `control\<id>.cmd`.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Bot Bridge CC Helper MCP server does

Bot Bridge CC Helper MCP server lets an MCP client dispatch coding tasks to a locally installed Windows desktop Helper. The extension and bundled bridge act as the front end; the separate Helper owns the task directories, runs Claude Code, and presents progress through its tray interface.

The bridge does not launch Claude Code directly. It communicates through files under the configured Helper home, normally `%USERPROFILE%\\cc-helper`. This makes it suitable when a bot or editor agent needs to hand work to a local process while retaining the ability to inspect or stop jobs.

The extension remains usable without the desktop Helper, but status and dispatch operations report that the Helper is unavailable instead of sending a task.

## How it works

A dispatch request creates a job JSON file containing an ID, title, and prompt in the `inbox` directory. The file is first written temporarily and then renamed, preventing the daemon from reading an incomplete job. The Helper detects the file, runs the requested work through Claude Code, and records execution data in its task folders.

Running tasks expose `status.json` and `progress.md`; completed tasks expose a final `status.json`. Stop requests create a `stop` command file in `control`. The bridge reads and writes only within the configured Helper home and validates task IDs before constructing paths.

Bot Bridge CC Helper MCP server adds no separate application protocol; it uses the same file bridge as the related Cursor and Grok Bot workflow. The extension itself makes no network requests, and it does not collect telemetry.

## Setup and configuration

Install the Bot Bridge CC Helper VS Code extension from a VSIX or, when available, the Marketplace. Separately install the Windows desktop Helper from the project homepage, keep its tray process running, and install the Claude Code CLI on the same machine.

VS Code 1.101 or newer is required because the extension uses VS Code's MCP server definition provider API. Node.js does not need a separate installation for the bridge because VS Code supplies an embedded Node runtime.

The extension provides these machine-scoped settings:

- `botbridge-cc-helper.enabled` enables or disables MCP server registration while leaving extension commands available.
- `botbridge-cc-helper.helperHome` selects the Helper directory; its default is `%USERPROFILE%\\cc-helper`.
- `botbridge-cc-helper.nodePath` selects the Node executable used to launch the bundled bridge instead of VS Code's runtime.

After installation, run the environment check command to verify the Helper folder and its `inbox`, `running`, `done`, and `control` directories. Start the MCP server from VS Code's MCP servers view and approve the trust prompt before using agent mode.

## Tools and capabilities

Bot Bridge CC Helper MCP server exposes five tools:

- `cc_helper_status` checks whether the Helper is installed and reports queued, running, and completed job counts.
- `cc_helper_dispatch` places one job in the local inbox and returns its task ID.
- `cc_helper_task_status` reads the selected task's status and, for active work, its progress file.
- `cc_helper_list_tasks` lists queued, active, and finished tasks.
- `cc_helper_stop` writes a stop request for a task to the control directory.

The extension also includes commands for environment checks, manual dispatch, opening the local Helper folder, refreshing the MCP registration, and opening the Helper homepage.

## Limitations and notes

The desktop Helper is not included in this repository and is required to execute jobs. The extension is not a Claude Code interface or fork, and it does not run Claude Code itself. The documented workflow is Windows-based.

Task data is stored as plain text on disk, so prompts should not contain API keys or other credentials. The extension does not delete or rewrite project work, but it does read and write task files beneath `helperHome`. Changing `helperHome` or `nodePath` at workspace scope is ignored; both settings are machine-scoped.

The free extension supports dispatch, progress observation, and stopping jobs. Token caps, stall timeouts, and phone notifications belong to the separately licensed Pro desktop Helper and are not enabled by this repository.

_Full upstream README: https://allmcps.com/mcp/bot-bridge-cc-helper/readme_