
Company News
AWS Security Hub Adds Socket for Supply Chain Security
Socket is now in the AWS Security Hub Extended plan. Adopt it through AWS, apply committed spend, and block malicious open source packages.
@buildpulse/mcp
Advanced tools
BuildPulse Model Context Protocol server — flaky test analytics, coverage, and CI run history as agent-callable tools.
Model Context Protocol server for the BuildPulse Platform API. Lets Claude Desktop, Cursor, Cline, Windsurf, Continue, ChatGPT (via MCP-enabled clients), and any other MCP-aware agent query your CI test analytics directly.
npx -y @buildpulse/mcp
Or pin globally:
npm install -g @buildpulse/mcp
The package downloads the matching native binary for your platform on first install. Supported platforms: macOS (arm64, x64), Linux (arm64, x64), Windows (x64).
You need a BuildPulse API token. Generate one at https://app.buildpulse.io → Organization Settings → API Tokens.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"buildpulse": {
"command": "npx",
"args": ["-y", "@buildpulse/mcp"],
"env": {
"BUILDPULSE_TOKEN": "your-40-char-hex-token"
}
}
}
}
Edit .cursor/mcp.json in your project (or ~/.cursor/mcp.json for
all projects):
{
"mcpServers": {
"buildpulse": {
"command": "npx",
"args": ["-y", "@buildpulse/mcp"],
"env": {
"BUILDPULSE_TOKEN": "your-40-char-hex-token"
}
}
}
}
Use the same JSON snippet — these clients all read mcpServers in
their respective config files.
| Tool | Purpose |
|---|---|
find_flaky_tests | Search a repo's flaky inventory. Filter by tags, recency, free-text. |
get_test_history | Recent disruption events for a specific test. |
list_recent_submissions | Recent CI runs for a repository. |
get_repo_flakiness | Current flakiness % (last 14 days). |
get_repo_coverage | Current coverage % (latest report). |
| Variable | Required | Default |
|---|---|---|
BUILDPULSE_TOKEN | yes | — |
PLATFORM_API_URL | no | https://platform.buildpulse.io |
authentication failed (401) — token is wrong, expired, or your
org has no active plan. Confirm by running:
curl -i -H "Authorization: token $BUILDPULSE_TOKEN" https://platform.buildpulse.io/api
Expected: HTTP/1.1 204 No Content.
MCP client shows "server failed to start" — open the integration's log panel. The stderr will tell you what's wrong (missing token, binary download failure, etc.).
Binary download failed during install — set
BUILDPULSE_MCP_SKIP_INSTALL=1 and build from source:
git clone https://github.com/BuildPulseLLC/buildpulse-mcp
cd platform-api && go build -o /usr/local/bin/buildpulse-mcp ./cmd/mcp
MIT. See LICENSE.
FAQs
BuildPulse Model Context Protocol server — flaky test analytics, coverage, and CI run history as agent-callable tools.
We found that @buildpulse/mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

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.

Company News
Socket is now in the AWS Security Hub Extended plan. Adopt it through AWS, apply committed spend, and block malicious open source packages.

Research
/Security News
Popular npm packages keyv and cacheable compromised.

Security News
A misconfiguration gave three Anthropic models internet access, and one, believing it was in a simulation, shipped a credential-stealing package to PyPI.