BuildPulse MCP server
online · 100% uptimeio.github.BuildPulseLLC/buildpulse-mcp·v0.1.7BuildPulse CI test analytics for AI agents — flaky tests, CI failures, flakiness, and code coverage.
0 stars44 downloads/wk
Reviews
Write oneNobody has reviewed BuildPulse yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
BuildPulse tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned15/25
- Live reliabilityremote reachable in 502ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 13 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: … "README.md" ], "scripts": { "postinstall": "node ./lib/install.js" }, "engines…
How BuildPulse compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 73% of 1,119 Developer tools servers
- Uptime
- 100%
- of our recent checks; the typical remote Developer tools server answers 100%
- Response time
- 769 ms
- faster than 13% of 443 Developer tools servers
- Downloads a week
- 44
- more than 32% of 436 Developer tools servers with a package
Install BuildPulse in Claude Code, Cursor or VS Code
claude mcp add --transport http buildpulse-mcp https://mcp.buildpulse.io/mcp
What the publisher says
From the BuildPulse repository's README, as published. We do not edit it. Read it on GitHub
Model Context Protocol server for the BuildPulse
Platform API. Surface flaky tests, CI run history, and coverage health
in Claude Desktop, Cursor, ChatGPT, Cline, Windsurf, Continue, Zed,
VS Code Copilot, and any other MCP-aware AI agent.
Quickstart
Hosted (recommended) — nothing to install, no API token. Your client opens a browser and you sign in with your BuildPulse account (Google, GitHub, Bitbucket, Apple, or email):
claude mcp add --transport http buildpulse https://mcp.buildpulse.io/mcpClaude.ai, ChatGPT, Cursor, VS Code: add https://mcp.buildpulse.io/mcp as an HTTP/remote MCP server and complete the sign-in when prompted.
Local stdio — for clients that only spawn a process, or for scripts and CI where a browser sign-in is not possible. This path needs an API token:
BUILDPULSE_TOKEN=bp_... npx -y @buildpulse/mcpSee Authentication for where tokens come from and when you need one.
Try asking
- "Why is CI red on web-client? Show me the failing tests from the last run."
- "Which tests in platform-api have been flakiest this week, and where do they fail?"
- "How well tested is agents? Give me flakiness and coverage."
- "Which tests failed in more than one of the last 10 runs of api?"
- "Triage the flaky tests in frontend and tell me which to quarantine first."
Install
npx -y @buildpulse/mcpOr pin globally:
npm install -g @buildpulse/mcpThe package downloads the matching native binary for your platform on first install. Supported platforms: macOS arm64/x64, Linux arm64/x64, Windows x64.
Authentication
There are two ways to authenticate, and most people only need the first.
Get a token at → Organization Settings → API Tokens. Tokens look like bp_<64 hex chars>; the older 40-character hex tokens still work. A token grants access to the same organizations your account does.
Configure
Hosted snippets sign you in via SSO. Stdio snippets need BUILDPULSETOKEN; replace bp... with your token.
Claude Code
Hosted (SSO, no token):
claude mcp add --transport http buildpulse https://mcp.buildpulse.io/mcpStdio (token):
claude mcp add buildpulse -e BUILDPULSE_TOKEN=bp_... -- npx -y @buildpulse/mcpClaude Desktop
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-03restoreC → Ascore 87: npm install lifecycle script present; npm install lifecycle script present
BuildPulse: common questions
- Is BuildPulse MCP server safe?
- Yes, by our scan: it is graded A (87/100). Read the BuildPulse safety report
- How do I install BuildPulse?
- It runs remotely at mcp.buildpulse.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does BuildPulse need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is BuildPulse maintained?
- The last commit was 44 days ago (2026-09-20). The latest release is v0.1.7.
- Is BuildPulse up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of BuildPulse?
- Servers from other publishers that do the same job: RepoPilot MCP server, Suvadu MCP server and Mergetrain MCP server.
- How does BuildPulse compare with other Developer tools MCP servers?
- safety score 87/100 (higher than 73% of 1,119 Developer tools servers); uptime 100% (of our recent checks; the typical remote Developer tools server answers 100%); response time 769 ms (faster than 13% of 443 Developer tools servers). Full comparison.
Alternatives to BuildPulse
Same job from other publishers: the closest match first, then the best rated.
- RepoPilotLocal, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.not reviewedGrowingA
SuvaduLocal shell history and AI agent sessions over MCP: search commands, failures, risk and git changesnot reviewedGrowingA
MergetrainQueue parallel-agent worktree branches, test together, serialize and recover Git pushes.not reviewedGrowingA- ZuulZuul CI — build failure analysis, log search, pipeline status, and job configurationnot reviewedGrowingA
- BitriseSet up & manage mobile CI/CD on Bitrise: build, test, distribute iOS, Android, Flutter, RN apps.not reviewedGrowingA
