Ext Ops Panel
Open dashboard
Comparison

pipedrive-webhooks vs CallRail MCP

pipedrive-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). CallRail MCP is an MCP server published by pghdma. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-23. 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-webhooksCallRail MCP
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 94
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.1
Downloads/month (PyPI): 582
Downloads/week (PyPI): 168
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.3.1
Downloads/month (PyPI): 582
Downloads/week (PyPI): 168
Forks (GitHub): 0
Stars (GitHub): 2
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-webhooks vs CallRail MCP
Factpipedrive-webhooksCallRail MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)94 (better)2 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (callrail-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/pghdma/callrail-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-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-webhooks

In its own words, on Community GitHub marketplaces:

Receive and authenticate Pipedrive webhooks. Use when setting up Pipedrive webhook handlers, debugging HTTP Basic Auth verification, or handling CRM events like create.deal, change.person, or delete.activity.

CallRail MCP

In its own words, on Official MCP Registry:

CallRail REST API v3: 57 tools for calls, leads, trackers, tags, users, and agency reporting.

How to run each

pipedrive-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install pipedrive-webhooks@webhook-skills

CallRail MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CALLRAIL_API_KEY=<YOUR_CALLRAIL_API_KEY>" --transport stdio callrail-mcp -- uvx callrail-mcp

Requires: CALLRAIL_API_KEY (secret)

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

The marketplaces of pipedrive-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: pipedrive-webhooks · What it can do: CallRail MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.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