MCP server for the BuildPulse Platform API that exposes flaky test data, CI run history, and coverage health to MCP-aware clients. It supports both stdio and hosted Streamable HTTP transports.
From the registry: BuildPulse CI test analytics for AI agents — flaky tests, coverage, and CI run history.
Please install the `buildpulse-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **BuildPulse API token** — Create a BuildPulse API token from BuildPulse at Organization Settings → API Tokens. Required for authentication. (https://app.buildpulse.io/)
- **Node.js and npm/npx** — Required to run the MCP server via the recommended npx install path.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@buildpulse/mcp"]
- required environment variables:
- `BUILDPULSE_TOKEN`: BuildPulse API token used to authenticate to the BuildPulse Platform API. (example: `<your-buildpulse-api-token>`)
- optional environment variables:
- `PLATFORM_API_URL`: Override the BuildPulse Platform API base URL. (example: `<your-platform-api-url>`)
Note: The README also documents a hosted Streamable HTTP endpoint at https://mcp.buildpulse.io/mcp, but no canonical headers/auth configuration is provided in the client config examples. Per the portable-install rule, prefer the universal stdio npx path.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.BUILDPULSE_TOKENrequiredBuildPulse API token used to authenticate requests.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.