Ext Ops Panel
Open dashboard
Comparison

dealhub-webhooks vs HubSpot MCP

dealhub-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). HubSpot MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-13. 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
Marketplacedealhub-webhooksHubSpot MCP
Community marketplace hookdeck/webhook-skills Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 101
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
Forks (GitHub): 18
Stars (GitHub): 76
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

dealhub-webhooks vs HubSpot MCP
Factdealhub-webhooksHubSpot MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)101 (better)76 (worse)
Forks (GitHub) (differs)16 (worse)18 (better)
Last release (differs)Not published2026-11-12
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/Servosity/msp-skills/releases/download/hubspot-v0.3.0/hubspot-mcp.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 2
Licence (differs)MITApache-2.0
Repository (differs)github.com/hookdeck/webhook-skillsgithub.com/servosity/msp-skills
Changes in the last 7 days (differs)015
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

dealhub-webhooks

In its own words, on Community GitHub marketplaces:

Receive and authenticate DealHub webhooks (DealHub CPQ / quote-to-revenue). Use when setting up a DealHub webhook handler, debugging the Authorization header DealHub sends (Token mode "Bearer <TOKEN>" or Basic mode "Basic <CREDENTIALS>"), or handling quote events like draftQuote, primaryQuote, quoteReady and quoteWon, plus version, user, productsUpload and DEALROOM_EVENT events. DealHub does not sign webhooks: there is no signature header or HMAC.

HubSpot MCP

In its own words, on Official MCP Registry:

Every HubSpot Sales Hub feature, plus offline cross-object queries, property-change-history

How to run each

dealhub-webhooks As a Claude Code plugin

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

HubSpot MCP As a Claude Code plugin

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

Requires: HUBSPOT_ACCESS_TOKEN (secret), HUBSPOT_MCP_HTTP_TOKEN (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 dealhub-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: dealhub-webhooks · What it can do: HubSpot 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. 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