io.github.codespar/mcp-bling vs BoondManager MCP Server
io.github.codespar/mcp-bling is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). BoondManager MCP Server is an MCP server published by fauguste. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-29. 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 |  io.github.codespar/mcp-bling |   BoondManager MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Downloads/month (npm): 112 Downloads/week (npm): 24 Forks (GitHub): 52 Stars (GitHub): 275 Not marked · First seen |
Listed Version: 2.15.2 Downloads/month (npm): 2 633 Downloads/week (npm): 283 Forks (GitHub): 17 Stars (GitHub): 21 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 | io.github.codespar/mcp-bling | BoondManager MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 275 (better) | 21 (worse) |
| Forks (GitHub) (differs) | 52 (better) | 17 (worse) |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (@codespar/mcp-bling) | On your machine (boondmanager-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 14, secrets among them: 5 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/codespar/mcp-dev-latam | github.com/fauguste/boondmanager-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
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
io.github.codespar/mcp-bling
MCP server for Bling — ERP: products, orders, invoices (NF-e/NFS-e), stock, AR/AP, webhooks
BoondManager MCP Server
MCP Server for BoondManager API - 182 tools, 12 prompts, 22 resources (ERP/CRM)
How to run each
io.github.codespar/mcp-bling As a local MCP server: npm package
claude mcp add --env "BLING_ACCESS_TOKEN=<YOUR_BLING_ACCESS_TOKEN>" --transport stdio mcp-bling -- npx -y @codespar/mcp-blingRequires: BLING_ACCESS_TOKEN (secret)
BoondManager MCP Server As a local MCP server: npm package
claude mcp add --transport stdio boondmanager-mcp-server -- npx -y boondmanager-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.codespar/mcp-bling asks for
BLING_ACCESS_TOKEN (secret)
Only BoondManager MCP Server asks for
BOOND_API_TOKEN (secret)BOOND_BASE_URLBOOND_CLIENT_KEY (secret)BOOND_CLIENT_TOKEN (secret)BOOND_DICTIONARY_OVERRIDESBOOND_MCP_CONFIRM_DELETEBOOND_MCP_DOMAINSBOOND_MCP_EXCLUDE_DOMAINSBOOND_MCP_OPERATIONSBOOND_MCP_PROFILEBOOND_MCP_READ_ONLYBOOND_PASSWORD (secret)
Show the remaining 2
BOOND_USERBOOND_USER_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.codespar/mcp-bling · What it can do: BoondManager MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.