HubSpot vs Clockify Time Tracking
HubSpot is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Clockify Time Tracking is an MCP server published by tracegazer. 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 |  Clockify Time Tracking | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.2 Downloads/month (PyPI): 158 Downloads/week (PyPI): 63 Forks (GitHub): 1 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 | Clockify Time Tracking |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app.hubspot.com/mcp/v1/http) | On your machine (clockify-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/tracegazer/clockify-mcp |
| 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.
Clockify Time Tracking
Clockify time-tracking MCP: 112 tools across 18 domains, read-only by default with opt-in writes.
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)
Clockify Time Tracking As a local MCP server: PyPI package
claude mcp add --env "CLOCKIFY_API_KEY=<YOUR_CLOCKIFY_API_KEY>" --transport stdio clockify-mcp -- uvx clockify-mcpRequires: CLOCKIFY_API_KEY (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 Clockify Time Tracking asks for
CLOCKIFY_ACCESS_MODECLOCKIFY_API_KEY (secret)CLOCKIFY_DEFAULT_WORKSPACE_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HubSpot · What it can do: Clockify Time Tracking · 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.