BuildPulse MCP Server

What the code does

We read the source, 9 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

postinstall: node ./lib/install.js

const child = spawn(binaryPath, process.argv.slice(2), {

  const outPath = path.join(__dirname, binaryName);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

claude mcp add buildpulse-mcp --transport http https://mcp.buildpulse.io/mcp

{
  "mcpServers": {
    "buildpulse-mcp": {
      "url": "https://mcp.buildpulse.io/mcp"
    }
  }
}

[mcp_servers.buildpulse-mcp]
url = "https://mcp.buildpulse.io/mcp"

{
  "mcpServers": {
    "buildpulse-mcp": {
      "url": "https://mcp.buildpulse.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "buildpulse-mcp": {
      "url": "https://mcp.buildpulse.io/mcp"
    }
  }
}

This one needs environment variables set before it will start: BUILDPULSE_TOKEN (BuildPulse API token (`bp_<64-hex>`; 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). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints