Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Windows-MCPHubSpot MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 SelectedChrome DevTools MCPMCP100 SelectedContext7 MCPMCP100 SelectedFirecrawl MCPMCP100 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Windows-MCPMCP100 Selected	HubSpot MCPMCP100 Selected
Task fit
Best for	Using an AI client to inspect and operate Windows applications when no safer application API exists	Querying CRM records, activities, marketing content, and organizational context Creating or updating supported CRM records and activities with confirmation Building managed AI workflows around HubSpot account data
Not ideal for	Deterministic automation that can be implemented through a documented API, CLI, or test framework	Clients that do not support OAuth 2.1 with PKCE Vector or semantic CRM search, which the documented backend does not provide
Avoid when	The desktop session contains sensitive applications, credentials, messages, or files outside the task	Existing HubSpot user permissions are broader than the intended agent workflow CRM or communication records cannot be shared with the chosen AI client Record creation, email logging, or meeting actions cannot require human approval
Provenance
Provenance details	Community implementation io.github.CursorTouch · Publisher source ↗	First-party MCP HubSpot · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 14, 2026 Package: Aug 1, 2026	Repo: Not documented Package: Not documented
Popularity evidence
GitHub stars	6,749 GitHub stars · checked 2026-08-14T18:46:26.000Z	Not documented
30-day package downloads	40,449 PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z	No reliable download data
External adoption evidence	github: repository stars: 6,749Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗ PyPI Stats: package downloads: 40,449Non-comparable contextual signal.PyPI Stats: package downloads · Provider last month · checked 2026-08-14T18:46:26.000ZEvidence source ↗	Not documented
Client coverage
Client coverage details	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Stdio has no network listener. Non-loopback HTTP requires an auth key or OAuth unless insecure access is explicitly allowed; IP allowlists, TLS, CORS, and host validation are documented.	OAuth 2.1 with PKCE is required. A HubSpot MCP auth app supplies client ID, client secret, and registered redirect URL; the user selects an account and grants available permissions.
Cost	The MIT-licensed project lists no MCP fee. Windows, Python, hosting, client, and model costs are separate.	HubSpot documents the remote MCP server as generally available to all HubSpot accounts without a separate MCP fee. HubSpot subscription features, API limits, integration hosting, and AI-client costs still apply.
Permissions	Runs with the invoking user's full Windows permissions, including PowerShell, files, registry, processes, UI input, screenshots, and web scraping; many actions are irreversible.	Read access includes CRM records, activities, marketing content, campaigns, and organizational context. Write access includes supported contacts, companies, deals, tickets, line items, products, calls, emails, meetings, notes, and tasks. Every action respects the authenticated HubSpot user's permissions.
Data handling	Processing is local. Telemetry excludes screenshots, state captures, arguments, and outputs but includes status, duration, tool and client information, anonymized sessions, and possibly paths in error messages.	HubSpot's hosted MCP service relays authorized CRM and activity data to the MCP client. Sensitive Data accounts block activity objects through MCP. Client credentials, OAuth tokens, retrieved records, and tool results must be protected by the integrating application.
Limitations
Tradeoffs	General computer-use reaches many applications, but visual automation is brittle and broad input control can produce high-impact unintended actions.	The GA hosted service removes local server maintenance but requires creation and management of an MCP auth app. Available scopes follow current server tools and user-granted permissions; newly added scopes can require reauthorization. HubSpot blocks activity objects through MCP when Sensitive Data is enabled, reducing exposure but also capability.
Risk context	It is not sandboxed and can delete files, alter registry or system settings, type into applications, and execute PowerShell. Use a VM or low-privilege account, backups, supervision, loopback binding, and disabled high-risk tools.	CRM and activity tools can expose personal and commercially sensitive data or create consequential customer records and communications. Use a dedicated auth app, narrow user permissions, secure PKCE and token storage, re-review scope changes, and confirm mutations. No MCP100 execution testing is claimed.
Evidence date
Editorial review	2026-08-11	2026-07-24
Candidate evidence	2026-08-14T18:46:26.000Z	2026-07-29T20:58:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →