Ext Ops Panel
Open dashboard
Comparison

merge-agent-handler vs HubSpot MCP

merge-agent-handler is a plugin bundle for AI coding tools published by merge-api. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-10-14. 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
Marketplacemerge-agent-handlerHubSpot MCP
Claude Code: claude-plugins-community Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Forks (GitHub): 12
Stars (GitHub): 59
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

merge-agent-handler vs HubSpot MCP
Factmerge-agent-handlerHubSpot MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)59 (better)
Forks (GitHub) (differs)0 (worse)12 (better)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/Servosity/msp-skills/releases/download/hubspot-v0.2.1/hubspot-mcp.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published6, secrets among them: 2
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITApache-2.0
Repository (differs)github.com/merge-api/ah-pluginsgithub.com/servosity/msp-skills
Changes in the last 7 days (differs)04
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

merge-agent-handler

In its own words, on Claude Code: claude-plugins-community:

Connect Claude Code and Cowork to hundreds of enterprise tools (Jira, Salesforce, HubSpot, Slack, Gong, Workday, etc.) via Merge Agent Handler. 18 MCP tools for managing users, tool packs, connectors, and calling enterprise APIs.

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

merge-agent-handler As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install merge-agent-handler@claude-community

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 merge-agent-handler publish no settings it asks for, so we do not compare settings.

What it can do: merge-agent-handler · What it can do: HubSpot MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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