local-ci vs BuildPulse
local-ci is a plugin bundle for AI coding tools published by MrPuls. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). BuildPulse is an MCP server published by BuildPulseLLC. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  local-ci |  BuildPulse |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.0.24 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.7 Downloads/month (npm): 486 Downloads/week (npm): 41 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | local-ci | BuildPulse |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.buildpulse.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mrpuls/local-ci | github.com/buildpulsellc/buildpulse-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
local-ci
Autonomously run CI/CD pipelines on your behalf. This gives Claude Code the ability to validate code in real target environments — different runtimes, OS images, or with real services like databases
BuildPulse
BuildPulse CI test analytics for AI agents — flaky tests, CI failures, flakiness, and code coverage.
How to run each
local-ci As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install local-ci@claude-communityBuildPulse As a remote MCP server
claude mcp add --transport http buildpulse-mcp https://mcp.buildpulse.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: BUILDPULSE_TOKEN (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only BuildPulse has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of local-ci publish no settings it asks for, so we do not compare settings.
What it can do: local-ci · What it can do: BuildPulse · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.