Ext Ops Panel
Open dashboard
Comparison

Pipedrive CRM vs Brandboom MCP by usefulapi

Pipedrive CRM is an MCP server published by ckalima. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Brandboom MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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

Where each is published
MarketplacePipedrive CRMBrandboom MCP by usefulapi
Official MCP Registry Listed
Version: 2.7.1
Downloads/month (npm): 954
Downloads/week (npm): 209
Forks (GitHub): 2
Stars (GitHub): 10
Not marked · First seen
Listed
Version: 1.2.5
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Listed
Version: 2.7.1
Downloads/month (npm): 954
Downloads/week (npm): 209
Forks (GitHub): 2
Stars (GitHub): 10
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

Pipedrive CRM vs Brandboom MCP by usefulapi
FactPipedrive CRMBrandboom MCP by usefulapi
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)10 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-11-07
Where it runs (differs)On your machine (@ckalima/pipedrive-mcp-server)Remote server (brandboom.usefulapi.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/ckalima/pipedrive-mcp-servergithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)010
First seen (differs)2026-10-112026-11-02
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 33 h ago returned HTTP 401

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

Pipedrive CRM

In its own words, on Official MCP Registry:

MCP server for Pipedrive CRM. 155 tools for deals, persons, organizations, activities, and more.

Brandboom MCP by usefulapi

In its own words, on Official MCP Registry:

Search showrooms, products, orders, customers, invoices and shipments in Brandboom.

How to run each

Pipedrive CRM As a local MCP server: npm package

Claude Code
claude mcp add --env "PIPEDRIVE_API_KEY=<YOUR_PIPEDRIVE_API_KEY>" --transport stdio pipedrive-mcp-server -- npx -y @ckalima/pipedrive-mcp-server

Requires: PIPEDRIVE_API_KEY (secret)

Brandboom MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http brandboom https://brandboom.usefulapi.io/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Brandboom MCP by usefulapi 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 Brandboom MCP by usefulapi publish no settings it asks for, so we do not compare settings.

What it can do: Pipedrive CRM · What it can do: Brandboom MCP by usefulapi · 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). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built