HubSpot vs Kaseya BMS
HubSpot is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Kaseya BMS is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  HubSpot |  Kaseya BMS |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.6 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 | Kaseya BMS |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Remote server (app.hubspot.com/mcp/v1/http) | On your machine (ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6) |
| 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: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/wyre-ai/kaseya-bms-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days 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.
Kaseya BMS
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
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)
Kaseya BMS As a local MCP server: Docker image
claude mcp add --env "KASEYA_BMS_API_TOKEN=<YOUR_KASEYA_BMS_API_TOKEN>" --env "KASEYA_BMS_K1_TOKEN=<YOUR_KASEYA_BMS_K1_TOKEN>" --env "KASEYA_BMS_TENANT_SUBDOMAIN=<YOUR_KASEYA_BMS_TENANT_SUBDOMAIN>" --transport stdio kaseya-bms-mcp -- docker run -i --rm -e KASEYA_BMS_API_TOKEN -e KASEYA_BMS_K1_TOKEN -e KASEYA_BMS_TENANT_SUBDOMAIN ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6Requires: KASEYA_BMS_API_TOKEN (secret), KASEYA_BMS_K1_TOKEN (secret), KASEYA_BMS_TENANT_SUBDOMAIN
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
Only HubSpot asks for
HUBSPOT_API_KEY (secret)
Only Kaseya BMS asks for
AUTH_MODEKASEYA_BMS_API_TOKEN (secret)KASEYA_BMS_K1_TOKEN (secret)KASEYA_BMS_TENANT_SUBDOMAINLOG_LEVELMCP_TRANSPORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HubSpot · What it can do: Kaseya BMS · 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.