Ext Ops Panel
Open dashboard
Comparison

Pipedrive MCP vs BoondManager MCP Server

Pipedrive MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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-19. 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 MCPBoondManager MCP Server
Official MCP Registry Listed
Version: 0.1.4
Forks (GitHub): 12
Stars (GitHub): 61
Not marked · First seen
Listed
Version: 2.15.2
Downloads/month (npm): 2 714
Downloads/week (npm): 562
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

Pipedrive MCP vs BoondManager MCP Server
FactPipedrive MCPBoondManager MCP Server
Marketplaces that list it22
Stars (GitHub) (differs)61 (better)21 (worse)
Forks (GitHub) (differs)12 (worse)17 (better)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/pipedrive-v0.1.4/pipedrive-mcp.mcpb)On your machine (boondmanager-mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 114, secrets among them: 5
Parts of the bundle (differs)Not a bundle1
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/servosity/msp-skillsgithub.com/fauguste/boondmanager-mcp-server
Changes in the last 7 days (differs)52
First seen2026-10-112026-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

Pipedrive MCP

In its own words, on Official MCP Registry:

Full Pipedrive CRUD plus a local SQLite pipeline copy: stale deals, forecasts, aging, dupes, rep

BoondManager MCP Server

In its own words, on Official MCP Registry:

MCP Server for BoondManager API - 182 tools, 12 prompts, 22 resources (ERP/CRM)

How to run each

Pipedrive MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install pipedrive@msp-skills

Requires: PIPEDRIVE_API_KEY (secret)

BoondManager MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio boondmanager-mcp-server -- npx -y boondmanager-mcp-server

Commands 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 Pipedrive MCP asks for

  • PIPEDRIVE_API_KEY (secret)
  • PIPEDRIVE_BASE_URL

Only BoondManager MCP Server asks for

  • BOOND_API_TOKEN (secret)
  • BOOND_BASE_URL
  • BOOND_CLIENT_KEY (secret)
  • BOOND_CLIENT_TOKEN (secret)
  • BOOND_DICTIONARY_OVERRIDES
  • BOOND_MCP_CONFIRM_DELETE
  • BOOND_MCP_DOMAINS
  • BOOND_MCP_EXCLUDE_DOMAINS
  • BOOND_MCP_OPERATIONS
  • BOOND_MCP_PROFILE
  • BOOND_MCP_READ_ONLY
  • BOOND_PASSWORD (secret)
Show the remaining 2
  • BOOND_USER
  • BOOND_USER_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Pipedrive MCP · 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.

Where the data comes from: how the catalog is built