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

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

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldApify MCP ServerMCP100 SelectedHubSpot MCPMCP100 Selected
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: Aug 14, 2026

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

3,664

GitHub stars · checked 2026-08-14T18:46:26.000Z

Not documented
External adoption evidence
  • github: repository stars: 3,664Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Not documented
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 noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationHosted 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.
CostActor 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.
PermissionsDynamically 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 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 handlingRequests 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 contextActor 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 review2026-08-112026-07-24
Candidate evidence2026-08-14T18:46:26.000Z2026-07-29T20:58:26.000Z

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

Read the evidence method →