Ext Ops Panel
Open dashboard
Comparison

HubSpot vs ai.backengine/backengine-mcp

HubSpot is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). ai.backengine/backengine-mcp is an MCP server published by backengine.ai. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceHubSpotai.backengine/backengine-mcp
Cursor: cursor/plugins Listed
Version: 1.0.1
Forks (GitHub): 1 107
Stars (GitHub): 11 352
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 8.1.1
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

HubSpot vs ai.backengine/backengine-mcp
FactHubSpotai.backengine/backengine-mcp
Marketplaces that list it11
Stars (GitHub) (differs)11 352 (better)1 (worse)
Forks (GitHub) (differs)1 107 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.hubspot.com)Remote server (backengine-prod.backengine.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsgithub.com/backengine-ai/backengine-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 31 h agonot checked yet

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 Cursor: cursor/plugins:

Search and update contacts, companies, deals, and tickets.

ai.backengine/backengine-mcp

In its own words, on Official MCP Registry:

Surface customer & prospect context from Slack, email, transcripts and tickets in any MCP client.

How to run each

HubSpot

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

ai.backengine/backengine-mcp As a remote MCP server

Claude Code
claude mcp add --transport http backengine-mcp https://backengine-prod.backengine.ai/mcp

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

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

What it can do: HubSpot · What it can do: ai.backengine/backengine-mcp · Compare two other plugins

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