BrainCloud MCP Helper vs Repomix

A side-by-side look at the BrainCloud MCP Helper and Repomix MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

BrainCloud MCP Helper logoBrainCloud MCP HelperDeveloper Tools · Local subprocess (stdio)Helper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code.56GoodAuth: not declaredRepomix logoRepomixDeveloper Tools · Local subprocess (stdio)Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search65GreatAuth: not declared

Verdict: choose BrainCloud MCP Helper for developer tools work as a local process; choose Repomix for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

BrainCloud MCP Helper logoChoose BrainCloud MCP Helper when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like status, pull, push.
Explore BrainCloud MCP Helper

Repomix logoChoose Repomix when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like pack_codebase, directory, compress.
Explore Repomix

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrainCloud MCP Helper logoBrainCloud MCP HelperRepomix logoRepomix
CategoryDeveloper ToolsDeveloper Tools
Quality signal56/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars129,014
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools423

Tools & capabilities

BrainCloud MCP Helper tools 4

  • statusDry-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.
  • pullApply 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.
  • pushApply 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).
  • syncFull 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).

Repomix tools 23

  • pack_codebasePackage a local code directory into a consolidated XML file for AI analysis
  • directoryAbsolute path to the directory to pack
  • compress(Optional, default: false) Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details. Reduces token usage by ~70% while preserving semantic meaning. Generally not needed since grep_repomix_output allows incremental content retrieval. Use…
  • includePatterns(Optional) Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). Only matching files will be processed.
  • ignorePatterns(Optional) Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js", "node_modules/**,dist/**"). These patterns supplement .gitignore, .ignore, and built-in exclusions.
  • outputPatterns(Optional) Per-file inclusion levels, mirroring the config-file `output.patterns` option. An array of `{ pattern, compress?, directoryStructureOnly? }` entries; the first matching pattern wins, `directoryStructureOnly` takes precedence over `compress`, and a match with neither flag forces full cont…
  • topFilesLength(Optional, default: 10) Number of largest files by size to display in the metrics summary for codebase analysis.
  • attach_packed_outputAttach an existing Repomix packed output file for AI analysis
  • pathPath to a directory containing repomix-output.xml or direct path to a packed repository XML file
  • pack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysis
  • remoteGitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch")
  • read_repomix_outputRead the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files.
  • +11 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

BrainCloud MCP Helper

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "braincloud-mcp-helper": {
      "command": "npx",
      "args": [
        "-y",
        "@braincloud/mcp-helper@latest"
      ]
    }
  }
}

Repomix

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "repomix": {
      "command": "npx",
      "args": [
        "-y",
        "repomix@latest"
      ]
    }
  }
}

Frequently asked questions

BrainCloud MCP Helper is categorized under Developer Tools and uses a local stdio subprocess. Repomix belongs to Developer Tools and uses a local stdio subprocess. Pick BrainCloud MCP Helper for developer tools work and Repomix for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

BrainCloud MCP Helper has no declared pricing — check the project's own site. Repomix has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add braincloud-mcp-helper and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, BrainCloud MCP Helper has a quality signal of 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Repomix has 65/100 (Great) with 4 views, 0 installs and 29,014 GitHub stars.