Linkbreakers MCP vs Claude Bridge
Linkbreakers MCP is an MCP server published by linkbreakers.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Claude Bridge is an MCP server published by constripacity. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |   Linkbreakers MCP |  Claude Bridge |
|---|---|---|
| Official MCP Registry | Listed Version: 1.183.3 Downloads/month (npm): 4 534 Downloads/week (npm): 1 635 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (PyPI): 375 Downloads/week (PyPI): 129 Forks (GitHub): 2 Stars (GitHub): 14 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.183.3 Downloads/month (npm): 4 534 Downloads/week (npm): 1 635 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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 | Linkbreakers MCP | Claude Bridge |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 14 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | 2026-10-22 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (claude-code-bridge) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/linkbreakers-com/agent-skills | github.com/constripacity/claude-bridge |
| Changes in the last 7 days (differs) | 12 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 6 days ago, requires a key | no remote endpoint we check |
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
Linkbreakers MCP
QR-driven customer-journey platform for tracked QR codes, short links, and analytics.
Claude Bridge
Durable local-first MCP relay for independent coding agents.
How to run each
Linkbreakers MCP As a remote MCP server
claude mcp add --transport http linkbreakers-mcp https://mcp.linkbreakers.com --header "Authorization: Bearer <YOUR_TOKEN>"Requires: LINKBREAKERS_API_TOKEN (secret), Authorization header
Claude Bridge As a local MCP server: PyPI package
claude mcp add --env "CLAUDE_BRIDGE_AUTH_TOKEN=<YOUR_CLAUDE_BRIDGE_AUTH_TOKEN>" --transport stdio claude-code-bridge -- uvx claude-code-bridge --stdioRequires: CLAUDE_BRIDGE_AUTH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Linkbreakers MCP 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
Only Linkbreakers MCP asks for
LINKBREAKERS_API_TOKEN (secret)
Only Claude Bridge asks for
CLAUDE_BRIDGE_AUTH_TOKEN (secret)CLAUDE_BRIDGE_DB
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Linkbreakers MCP · What it can do: Claude Bridge · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.