brainCloud MCP Helper

com.braincloudserversPublished by braincloudservers.comv6.0.0Updated Oct 24, 2026

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

The publisher's own server: BrainDog

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

A local stdio MCP server that gives AI clients filesystem access to sync brainCloud cloud-code scripts with a local folder and git.

What you can do
Check sync state: dry-run classification of every script as in-sync, pull, push, conflict, new or delete, without writing anything (status). Pull changes: apply brainCloud-to-local updates for non-conflicting scripts, with local deletes only when allowDeletes is set. Push changes: apply local-to-brainCloud updates for non-conflicting scripts through one bulk import. Full sync: two-way pull and push with a three-way merge for scripts changed on both sides, writing git-style conflict markers locally and reporting them. All tools take a local sync folder, a short-lived ticket and an optional branch name.
When to use it
Use it when you keep brainCloud cloud-code scripts in a local git repository and want an AI assistant to check, pull, push or merge them against brainCloud without moving bulk script data through the model's context.
Requirements
Runs locally over stdio, typically launched with npx from the npm package, so Node.js is needed. It needs a local sync folder and a short-lived, app-scoped ticket obtained from the hosted braincloud-mcp getSyncTicket tool; read tickets cover status and pull, write tickets cover push and sync. It is meant to be paired with that hosted server.
Before you install
Push and sync write to brainCloud and can change or delete cloud-code scripts; deletes in either direction happen only with allowDeletes, so leave it off unless intended. Sync writes git-style conflict markers into local files. The helper stores no credentials itself but handles tickets passed in by the assistant, so treat them as secrets. Bulk script data goes directly to the Builder API rather than through the model.

Installation

In SourceWeft

  1. Open brainCloud MCP Helper in the dashboard and add it to a workspace.
  2. 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

@braincloud/mcp-helper

A local stdio MCP server that gives AI clients (Claude Code, Cursor, Codex, …) filesystem access for brainCloud cloud-code sync.

It is deliberately trustless: it never authenticates to brainCloud on its own and stores no credential. Every Builder API call is driven by a short-lived, app-scoped ticket the AI obtains from the hosted braincloud-mcp's getSyncTicket tool and passes in. Bulk script data flows helper → Builder API directly — never through the AI's context.

Format and sync logic come from @braincloud/cloudsync-core; this package is the Node filesystem + MCP shell around it.

Tools

ToolTicketWhat it does
statusreadDry-run: classify every script (in-sync / pull / push / conflict / new / delete). No writes.
pullreadApply brainCloud → local for non-conflicting changes. Local deletes only with allowDeletes.
pushwriteApply local → brainCloud for non-conflicting changes via one bulk import (addAndUpdateOnly).
syncwriteFull two-way sync: pull + push + 3-way merge for scripts changed on both sides (merge base recovered from brainCloud version history). Clean merges are applied + pushed; real conflicts get git-style <<<<<<< markers written locally and reported in conflicted. Deletes both ways only with allowDeletes.

All take rootDir (the local sync folder), ticket (from getSyncTicket), and an optional branch (defaults to the current git branch from .git/HEAD). pull/status work with a read ticket; push/sync need a write ticket. In pull/push, conflicts and opposite-direction changes are never auto-applied — only sync reconciles both directions and merges.

Configure as an MCP server

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

npx @latest keeps the helper current on each launch; pin a version for CI. Pair it with the hosted braincloud-mcp (which vends the tickets and runs the live-lock policy).

Develop

bash
npm installnpm run build --workspace @braincloud/cloudsync-core   # helper depends on the built corenpm test  --workspace @braincloud/mcp-helpernpm run build --workspace @braincloud/mcp-helper

Source: packages/mcp-helper/README.md at commit 921d3a3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v6.0.0LatestSep 16, 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

Other Brain integrations