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

Apify MCP ServerHubSpot MCP

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

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedGoogle Search Console MCP Server for SEOsMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Apify MCP ServerMCP100 Recommended	HubSpot MCPMCP100 Recommended
Task fit
Best for	Running Apify Store Actors and retrieving their datasets through a hosted or local MCP connection	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	Simple page retrieval that does not justify an Apify account, Actor selection, and usage-based execution	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 target site's terms, privacy requirements, or your organization prohibit the proposed extraction	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 com.apify · Publisher source ↗	First-party MCP HubSpot · Publisher source ↗
Maintenance
Maintenance details	Repo: Sep 23, 2026 Package: Sep 21, 2026	Repo: Not documented Package: Not documented
Popularity evidence
GitHub stars	8,235 GitHub stars · checked 2026-09-24T04:14:39.546000Z	Not documented
Package downloads / 30 days	103,470 package downloads / 30 days · checked 2026-09-24T04:23:13.539000Z	No reliable download data
Client coverage
Client coverage details	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP	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	Hosted mode supports OAuth or Authorization Bearer APIFY_TOKEN; local stdio uses APIFY_TOKEN. Discovery tools can be unauthenticated, and agentic payment tokens are additional alternatives.	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	Actor and platform usage is chargeable according to Actor pricing; even free Actors incur platform usage. x402, Skyfire, and AGI payment paths are documented; no fixed MCP fee is stated.	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	Dynamically exposes Apify Actors, including web, social, maps, and e-commerce scrapers, plus run, dataset, key-value-store, and documentation tools. call-actor executes external Actors.	Read and write availability is governed by the MCP app's granted scopes together with the connected user's HubSpot permissions. Supported actions can include CRM records, activities, marketing content, and selected mutations; do not describe access as an over-specific universal intersection beyond those app scopes and user permissions.
Data handling	Requests and Actor inputs are sent to Apify; run results can be stored in Apify datasets and key-value stores. Telemetry is enabled by default and stdio uses Sentry; detailed retention is not documented.	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	Thousands of Actors broaden coverage, but each Actor has its own inputs and trust surface and Apify compute or proxy usage may incur charges.	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	Actor execution can scrape external sites, process personal or regulated data, incur spend, and return untrusted content. Restrict tools, use scoped tokens, review Actor pricing and terms, and control telemetry and storage.	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-09-24T04:25:05.554391Z	2026-09-24T04:25:05.554391Z

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

Read the evidence method →