🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

@braincloud/mcp-helper

Package Overview
Dependencies
Maintainers
7
Versions
11
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@braincloud/mcp-helper

Local stdio MCP server giving AI clients filesystem access for brainCloud cloud-code sync. Authenticates to brainCloud only via a short-lived ticket vended by the hosted braincloud-mcp.

Source
npmnpm
Version
0.2.0
Version published
Weekly downloads
108
-41.94%
Maintainers
7
Weekly downloads
 
Created
Source

@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

{
  "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

npm install
npm run build --workspace @braincloud/cloudsync-core   # helper depends on the built core
npm test  --workspace @braincloud/mcp-helper
npm run build --workspace @braincloud/mcp-helper

Keywords

braincloud

FAQs

Package last updated on 28 Jun 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts