GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 3 days ago
Install
brainCloud MCP Helper
Overview
Description from the maker (original English)
Helper for brainCloud MCP that gives it local file access, enabling easy git sync of cloud code.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 0 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"braincloud-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
}Run this in your terminal
claude mcp add braincloud-helper -- npx -y @braincloud/mcp-helperOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"braincloud-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"braincloud-helper": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ! Caution
Maker matches the repo
The publisher (braincloudservers.com) is not the repo owner (getbraincloud); someone else may have listed it
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 1392 servers in this category
- Published to the registry more recently than 31% of the other 1392 servers in this category
- Basic checks equal to or better than 22% of the other 1392 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is brainCloud MCP Helper safe?
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (6.0.0) reached the registry 4 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 15 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@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
| Tool | Ticket | What it does |
|---|---|---|
status | read | Dry-run: classify every script (in-sync / pull / push / conflict / new / delete). No writes. |
pull | read | Apply brainCloud → local for non-conflicting changes. Local deletes only with allowDeletes. |
push | write | Apply local → brainCloud for non-conflicting changes via one bulk import (addAndUpdateOnly). |
sync | write | Full 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 installnpm 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