HubSpot vs event-outbound
HubSpot is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). event-outbound is a plugin bundle for AI coding tools published by luminik-io. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  event-outbound | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.5 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | HubSpot | event-outbound |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app.hubspot.com/mcp/v1/http) | Installs as a plugin bundle |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/luminik-io/event-outbound-skill |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 7 h ago | no 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
Unite marketing, sales, and customer service with AI-powered automation, lead management, and comprehensive analytics.
event-outbound
Create buyer-first email and LinkedIn outreach for B2B trade shows and conferences. Give event details, ICP, target personas, and sender context. event-outbound drafts pre-event, day-of, and post-event touches, then validates each one locally for channel length, subject quality, inbox preview, buyer focus, CTA clarity, forced event phrasing, and common AI-sales cliches. Built by Luminik from 20K+ outbound touches reviewed across 50+ events. Runs inside Claude Code with no extra API key.
How to run each
HubSpot As a remote MCP server
claude mcp add --transport http hubspot https://app.hubspot.com/mcp/v1/httpRequires: HUBSPOT_API_KEY (secret)
event-outbound As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install event-outbound@claude-communityCommands 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 event-outbound publish no settings it asks for, so we do not compare settings.
What it can do: HubSpot · What it can do: event-outbound · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.