Helper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code.
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @braincloud/mcp-helper
MCP client config
{
"mcpServers": {
"braincloud-mcp-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
}A local, trustless MCP server that lets AI coding assistants (Claude Code, Cursor, Codex, …) sync brainCloud cloud-code scripts to and from your filesystem and git repo.
It never authenticates to brainCloud on its own and stores no credentials. Every Builder API call
is driven by a short-lived, app-scoped ticket that the AI obtains from the hosted
braincloud-mcp's getSyncTicket tool and passes in — script content flows helper → Builder API
directly, never through the AI's context.
This is an npm workspace with two packages:
| Package | What it is |
|---|---|
@braincloud/mcp-helper | The MCP server itself — status / pull / push / sync tools, installable via npx -y @braincloud/mcp-helper@latest. |
@braincloud/cloudsync-core | Host-agnostic sync/format logic (the .ccjs / .bcsync / .bcsync.local on-disk contract) shared with the VS Code extension. |
See each package's README for tool details, configuration, and the on-disk format.
Full setup and usage guide: Syncing cloud code to local files with the brainCloud MCP helper
npm install
npm run build # builds all workspaces
npm test # tests all workspaces
See RELEASING.md for the release process.