Ext Ops Panel
Open dashboard
Comparison

clay vs hubspot-partner

clay is a plugin bundle for AI coding tools published by clay-run. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). hubspot-partner is a plugin bundle for AI coding tools published by hubspot. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
Marketplaceclayhubspot-partner
Claude Code: claude-plugins-official Listed
Version: 2.26.0
Forks (GitHub): 22
Stars (GitHub): 138
Not marked · First seen
Not listed
Community marketplace hubspot/hubspot-mcp-plugins Not listed Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 4
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

clay vs hubspot-partner
Factclayhubspot-partner
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)138 (better)4 (worse)
Forks (GitHub) (differs)22 (better)0 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.hubspot.com/anthropic)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)374
LicenceNot statedNot stated
Repository (differs)github.com/clay-run/agent-pluginsgithub.com/hubspot/hubspot-mcp-plugins
Changes in the last 7 days (differs)12
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 h ago

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

clay

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

Work with Clay from Claude Code: set up and sign in to the clay CLI, query and analyze Clay tables, search Clay's GTM database for people and companies, manage audiences, signals, routines and workflows, and draft and review Sequencer campaigns. Includes hooks that auto-approve the plugin's own clay CLI calls and Clay skills; requires a Clay account.

hubspot-partner

In its own words, on Community GitHub marketplaces:

HubSpot Solutions Partner tools for managing your book of business — a portfolio pulse across your PARTNER_CLIENT records.

How to run each

clay As a Claude Code plugin

Claude Code
/plugin install clay@claude-plugins-official

hubspot-partner As a Claude Code plugin

Claude Code
/plugin marketplace add hubspot/hubspot-mcp-plugins
/plugin install hubspot-partner@hubspot-claude-plugins

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

Only hubspot-partner 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

Neither one's marketplaces publish the settings it asks for.

What it can do: clay · What it can do: hubspot-partner · Compare two other plugins

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