BuildPulse MCP Server

BuildPulse CI test analytics for AI agents — flaky tests, CI failures, flakiness, and code coverage.

Local + remotestreamable-httpstdio

What is the BuildPulse MCP Server?

BuildPulse is an MCP integration. BuildPulse CI test analytics for AI agents — flaky tests, CI failures, flakiness, and code coverage.

Hosted connection

The registry lists a streamable-http connection at https://mcp.buildpulse.io/mcp. The endpoint declares these request headers: Authorization.

Packages and local setup

The published npm package is @buildpulse/mcp, version 0.1.7. Its declared MCP transport is stdio.

The package declares BUILDPULSE_TOKEN (required): BuildPulse API token (bp_ ; legacy 40-hex tokens also accepted). Create one at buildpulse.io → Organization Settings → API Tokens.; PLATFORM_API_URL: Override the platform API base URL. Default: https://platform.buildpulse.io.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.7 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related analytics & reporting MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
BUILDPULSE_TOKENBuildPulse API token (bp_ ; legacy 40-hex tokens also accepted). Create one at buildpulse.io → Organization Settings → API Tokens.Yes
PLATFORM_API_URLOverride the platform API base URL. Default: https://platform.buildpulse.ioOptional