Buildpulse Mcp
Let your agent query flaky tests, coverage trends, and CI history from BuildPulse instead of digging through GitHub Actions logs by hand.
Overview
BuildPulse MCP is a MCP server for the Ship phase that exposes flaky-test detection, coverage, and CI run history from BuildPulse to AI agents.
What is this MCP server?
- Surfaces BuildPulse CI analytics: flaky tests, coverage, and run history to agents
- Supports remote streamable-http MCP at https://mcp.buildpulse.io/mcp with Bearer auth
- Also ships npm stdio package @buildpulse/mcp (version 0.1.5)
- Requires 40-character BUILDPULSE_TOKEN from app.buildpulse.io organization settings
- Optional PLATFORM_API_URL override defaulting to https://platform.buildpulse.io
- Server package version 0.1.5 (@buildpulse/mcp)
- Remote MCP endpoint https://mcp.buildpulse.io/mcp
- API token is 40 characters per environment variable documentation
What problem does it solve?
Solo builders waste hours replaying CI logs when flaky tests and missing coverage context are buried across many workflow runs.
Who is it for?
Small teams and solo devs already on BuildPulse who want MCP-driven debugging of CI instability inside Claude Code or Cursor.
Skip if: Projects with no CI, no BuildPulse account, or needs for local-only test execution without a SaaS analytics backend.
What do I get? / Deliverables
After you connect with a BuildPulse token, your agent can pull structured test analytics so you prioritize fixes and unblock releases faster.
- Agent-queryable flaky test and coverage insights tied to CI history
- Faster triage narratives when diagnosing repeated red builds
- Documented dual transport setup (remote MCP URL or local npm server 0.1.5)
Recommended MCP Servers
Journey fit
CI reliability problems surface when you are trying to ship confidently; flaky tests are a ship-phase gate, not an abstract infra hobby. Testing subphase is the canonical shelf for analytics about test failures, coverage, and run history that unblock green builds.
How it compares
CI analytics MCP bridge, not an in-repo test framework or generic GitHub MCP clone.
Common Questions / FAQ
Who is BuildPulse MCP for?
It is for developers using BuildPulse who want agents to read flaky-test and coverage intelligence instead of manually searching CI dashboards.
When should I use BuildPulse MCP?
Use it during ship testing stabilization and ongoing operate iterations whenever CI goes red and you need historical flaky-test context.
How do I add BuildPulse MCP to my agent?
Either point your client at the remote MCP URL https://mcp.buildpulse.io/mcp with Authorization Bearer plus your 40-char token, or install @buildpulse/mcp over stdio with BUILDPULSE_TOKEN set from app.buildpulse.io.