HubSpot vs PlanVortex
HubSpot is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). PlanVortex is an MCP server published by taliasoftworks. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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
| Marketplace |  PlanVortex | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.11.1 Downloads/month (npm): 2 258 Downloads/week (npm): 644 Forks (GitHub): 0 Stars (GitHub): 0 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 | PlanVortex |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| 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) | On your machine (planvortex-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 6, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/taliasoftworks/planvortexmcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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.
PlanVortex
Schedule posts, read comments and answer messages across all your social networks.
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)
PlanVortex As a local MCP server: npm package
claude mcp add --env "PLANVORTEX_CLIENT_ID=<YOUR_PLANVORTEX_CLIENT_ID>" --env "PLANVORTEX_CLIENT_SECRET=<YOUR_PLANVORTEX_CLIENT_SECRET>" --transport stdio planvortex -- npx -y planvortex-mcpRequires: PLANVORTEX_CLIENT_ID, PLANVORTEX_CLIENT_SECRET (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
Only HubSpot asks for
HUBSPOT_API_KEY (secret)
Only PlanVortex asks for
PLANVORTEX_CLIENT_IDPLANVORTEX_CLIENT_SECRET (secret)PLANVORTEX_MCP_ALLOW_AIPLANVORTEX_MCP_READ_ONLYPLANVORTEX_MCP_UPLOAD_DIRSPLANVORTEX_ORGANIZATION_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HubSpot · What it can do: PlanVortex · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.