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 fieldPlaywright MCPMCP100 RecommendedHubSpot MCPMCP100 Recommended
Task fit
Best for
  • Inspecting and testing web interfaces through accessibility snapshots
  • Reproducing browser journeys in a dedicated test profile
  • 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
  • API-only testing that does not need a browser
  • Unattended access to a personal browsing profile
  • 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 workflow cannot permit an agent to navigate, type, click, upload files, or read page content
  • You cannot isolate sensitive authenticated sessions from the agent-controlled browser
  • 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

Microsoft · Publisher source ↗

First-party MCP

HubSpot · Publisher source ↗

Maintenance
Maintenance details

Repo: Sep 18, 2026

Package: Sep 21, 2026

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

37,525

GitHub stars · checked 2026-09-24T04:14:16.452000Z

Not documented
Package downloads / 30 days

23,800,747

package downloads / 30 days · checked 2026-09-24T04:17:39.045000Z

No reliable download data
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 noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe server itself does not require a service account for local stdio use, but websites opened in the controlled browser may use cookies or other authenticated browser state.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 first-party open-source package lists no MCP server usage fee. Normal internet, hosted-client, proxy, or third-party website costs can still apply.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.
PermissionsThe exposed tools can navigate pages, interact with elements, enter text, upload files, inspect network activity, and optionally use additional browser capabilities.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 handlingPage text, accessibility snapshots, console output, network details, uploaded paths, and browser state may be returned to the connected MCP client. Isolated mode keeps the temporary profile in memory; persistent mode stores browser state on disk.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
  • A persistent profile is convenient but can retain cookies and authenticated state between sessions.
  • Origin allow/block options reduce accidental access but the publisher explicitly says they are not a security boundary.
  • 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 contextPlaywright MCP is not a security boundary. Secret replacement or masking is a convenience feature, not a security boundary. Prefer an isolated browser profile, non-sensitive test accounts, narrow destinations, minimal optional permissions, and client-side approval controls.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-09-24T04:25:05.554391Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →