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 fieldNotion MCPMCP100 SelectedHubSpot MCPMCP100 Selected
Task fit
Best for
  • Reading and updating explicitly shared Notion pages
  • Markdown-oriented page workflows
  • Teams able to create a dedicated least-privilege integration
  • 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
  • Whole-workspace access without page scoping
  • Stable local-server APIs with no migration monitoring
  • Workflows that only need occasional manual Notion lookup
  • Clients that do not support OAuth 2.1 with PKCE
  • Vector or semantic CRM search, which the documented backend does not provide
Avoid when
  • Sensitive workspace content cannot be exposed to the connected model/client
  • You cannot create a dedicated read-only integration or restrict page access
  • You depend on removed pre-2.0 database tool names
  • 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

First-party MCP

Notion · Publisher source ↗

First-party MCP

HubSpot · Publisher source ↗

Maintenance
Maintenance details

Repo: Jul 25, 2026

Package: Jul 25, 2026

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

4,594

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

Not documented
30-day package downloads

624,402

30-day package downloads · checked 2026-07-29T17:30:00.000Z

No reliable download data
External adoption evidence
  • npm: package downloads: 624,402Exact attributable signal.npm: package downloads · Admission snapshot · checked 2026-07-29T17:30:00.000ZEvidence source ↗
  • github: repository stars: 4,594Exact 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
AuthenticationThe supported hosted service uses OAuth. The documented local server uses NOTION_TOKEN or OPENAPI_MCP_HEADERS; HTTP transport has a separate bearer token and supports carefully configured per-request Notion token passthrough.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.
CostThe local server is MIT licensed. A Notion account and workspace plan are required, and Notion plan/API limits apply; hosted MCP-specific charges were not established in the reviewed materials.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.
PermissionsLocal access is limited by the Notion integration capabilities and pages connected to that integration. Read-only capability is available; write-capable tools can create or update workspace content. Local HTTP transport requires bearer authentication unless an explicitly unsafe flag disables it.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 handlingPage/database content accessible to the integration can be returned to the MCP client and model. The local server calls Notion APIs; hosted Notion MCP additionally processes requests through Notion's remote service.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
  • Hosted OAuth is actively supported and easier; the local repository warns it may be sunset.
  • Write capability enables useful edits but raises deletion, overwrite, and prompt-injection risk.
  • Version 2 changed database operations to data-source tools, requiring updates to hardcoded prompts.
  • 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 contextWorkspace content may be read or modified within the integration's reach. Use a dedicated integration, Read content only where possible, explicitly connect only needed pages, avoid unsafe HTTP auth disabling, and monitor hosted/local migration guidance.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-07-242026-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 →