NestDaddy

BuildPulse

io.github.BuildPulseLLC/buildpulse-mcp · v0.2.0

BuildPulse for AI agents: CI runner usage, cost and savings, plus flaky tests, failures, coverage.

Connect Remote server

Terminal
claude mcp add --transport http buildpulse-mcp https://mcp.buildpulse.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "buildpulse-mcp": {
      "url": "https://mcp.buildpulse.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "buildpulse-mcp": {
      "type": "http",
      "url": "https://mcp.buildpulse.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.buildpulse.io/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server asks for a key before it lists its tools. Connect it with your own key to see them.

Headers

NameDescription
Authorization
Required, secret
Bearer <BuildPulse API token> (`bp_<64-hex>`; legacy 40-hex tokens also accepted). Or use OAuth 2.1 — see /.well-known/oauth-authorization-server for the discovery document.

Details

Endpointhttps://mcp.buildpulse.io/mcp (Streamable HTTP)
Package@buildpulse/[email protected] (NPM, stdio)
First published5 Nov 2026
Last updated5 Nov 2026
Registry nameio.github.BuildPulseLLC/buildpulse-mcp

More developer tools servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.