Azure DevOps (ADO) vs BrainCloud MCP Helper
A side-by-side look at the Azure DevOps (ADO) and BrainCloud MCP Helper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Azure DevOps (ADO)Developer Tools · Local subprocess (stdio)The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.55GoodAuth: not declaredVerdict: choose Azure DevOps (ADO) for developer tools work as a local process; choose BrainCloud MCP Helper 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?
AChoose Azure DevOps (ADO) when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Azure DevOps (ADO) | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,068 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Azure DevOps (ADO) | View BrainCloud MCP Helper |
Tools & capabilities
Azure DevOps (ADO) tools
No tool names declared yet. Check the project README from the listing page.
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).
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.
Azure DevOps (ADO)
{
"mcpServers": {
"azure-devops-ado": {
"command": "npx",
"args": [
"-y",
"@azure-devops/mcp"
]
}
}
}
BrainCloud MCP Helper
{
"mcpServers": {
"braincloud-mcp-helper": {
"command": "npx",
"args": [
"-y",
"@braincloud/mcp-helper@latest"
]
}
}
}
Frequently asked questions
Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. BrainCloud MCP Helper belongs to Developer Tools and uses a local stdio subprocess. Pick Azure DevOps (ADO) for developer tools work and BrainCloud MCP Helper 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.
Azure DevOps (ADO) is listed as free. BrainCloud MCP Helper 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 azure-devops-ado and braincloud-mcp-helper as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Azure DevOps (ADO) has a quality signal of 55/100 (Good) with 6 views, 0 installs and 2,068 GitHub stars. BrainCloud MCP Helper has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.