# brainCloud MCP Helper [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/getbraincloud/braincloud-mcp-helper  
**GitHub Stars:** 1  
**npm Downloads (last month):** 368  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/braincloud-mcp-helper

## Description
Helper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code.

## Tools
Capabilities this server exposes over MCP:

- **status** — Dry-run: classify every cloud-code script for the branch (in-sync / pull / push / conflict / pull-new / push-new / delete-local / delete-remote). Always safe — no writes. Use a "read" ticket from getSyncTicket.
- **pull** — Apply brainCloud → local for non-conflicting changes (pull / pull-new). Conflicts and local-only changes are left untouched and reported in "skipped". Local deletes only happen with allowDeletes=true. Use a "read" ticket from getSyncTicket.
- **push** — Apply local → brainCloud for non-conflicting changes (push / push-new) via one bulk import (mode addAndUpdateOnly — never deletes). Conflicts and remote-only changes are left untouched and reported in "skipped". Requires a "write" ticket from getSyncTicket (the hosted MCP refuses a write ticket for a live-locked app).
- **sync** — Full bidirectional sync for the branch: pulls non-conflicting remote changes, pushes non-conflicting local changes, and 3-way-merges scripts changed on BOTH sides (using brainCloud version history for the merge base). Cleanly-merged scripts are written locally and pushed; genuine conflicts get git-style <<<<<<< markers written into the file and are reported in "conflicted" for you to resolve, then re-run sync. Deletions (delete-local / delete-remote) are applied only when allowDeletes=true. Requires a "write" ticket from getSyncTicket (refused for a live-locked app).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "braincloud-mcp-helper": {
    "command": "npx",
    "args": ["-y","@braincloud/mcp-helper@latest"]
  }
}
```

## Documentation

## What brainCloud MCP Helper does

The brainCloud MCP Helper MCP server connects an MCP-capable coding assistant to brainCloud cloud-code files on a local filesystem. It supports two sides of the synchronization workflow: the brainCloud Builder API and a local directory that can also be tracked in a git repository.

The package is intended for assistants such as Claude Code, Cursor, and Codex. A developer can use it to inspect synchronization state, download cloud-code scripts, upload local changes, or run the available synchronization operation. The repository also contains a reusable cloudsync-core package with the on-disk rules shared by the helper and the VS Code extension.

## How it works

The brainCloud MCP Helper MCP server does not log in to brainCloud by itself. Instead, the AI obtains a short-lived ticket from the hosted braincloud-mcp server's `getSyncTicket` tool and passes that ticket to the helper. Each ticket is scoped to an app and drives the corresponding Builder API request.

Script contents are transferred directly between the helper and the Builder API. They do not pass through the assistant's context. The helper also does not retain credentials, which keeps authentication outside the local server's responsibilities.

Local synchronization follows the repository's file contract. The supported on-disk elements include `.ccjs`, `.bcsync`, and `.bcsync.local` files. These files can be placed in a git repository so cloud-code changes can be reviewed and versioned with the rest of a codebase.

## Setup and configuration

Install the MCP server from npm with the package command shown by the project:

```bash
npx -y @braincloud/mcp-helper@latest
```

The repository is organized as an npm workspace. For local development, install dependencies, build all workspaces, and run the test suite:

```bash
npm install
npm run build
npm test
```

Authentication is supplied at operation time through the ticket from hosted braincloud-mcp rather than through stored credentials.

## Tools and capabilities

The brainCloud MCP Helper MCP server provides these tools:

- `status` checks synchronization state.
- `pull` brings cloud-code scripts into the local file representation.
- `push` sends local script changes to the Builder API.
- `sync` performs the server's synchronization workflow.

The helper package is `@braincloud/mcp-helper`. The separate `@braincloud/cloudsync-core` package contains host-agnostic synchronization and formatting logic, including the local file contract.

## Limitations and notes

The helper is not a standalone brainCloud authentication client. It requires a ticket supplied by the hosted braincloud-mcp flow, and the ticket must be short-lived and app-scoped. It also does not store credentials.

Consult the linked setup guide and package README for those operational details. The repository's stated scope is cloud-code synchronization; it does not describe synchronization for other brainCloud resources.

_Full upstream README: https://allmcps.com/mcp/braincloud-mcp-helper/readme_