Ext Ops Panel
Open dashboard
Comparison

HubSpot vs pipedrive-webhooks

HubSpot is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). pipedrive-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
MarketplaceHubSpotpipedrive-webhooks
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 92
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

HubSpot vs pipedrive-webhooks
FactHubSpotpipedrive-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub92
Forks (GitHub) (differs)No figure on GitHub16
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.hubspot.com/mcp/v1/http)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21
Endpoint at the last check (differs)Responded 37 h agono 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

HubSpot

In its own words, on Docker MCP Catalog:

Unite marketing, sales, and customer service with AI-powered automation, lead management, and comprehensive analytics.

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.

How to run each

HubSpot As a remote MCP server

Claude Code
claude mcp add --transport http hubspot https://app.hubspot.com/mcp/v1/http

Requires: HUBSPOT_API_KEY (secret)

pipedrive-webhooks As a Claude Code plugin

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

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

Only HubSpot 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 pipedrive-webhooks publish no settings it asks for, so we do not compare settings.

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

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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