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

WordPress Remote MCPHubSpot 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	WordPress Remote MCPShortlist candidate	HubSpot MCPMCP100 Recommended
Task fit
Best for	WordPress developers/operators who need a remote MCP proxy to a WordPress site using the site's existing user/capability model.	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	Users who want a zero-configuration hosted WordPress service or who cannot safely grant the AI client the underlying WordPress account's capabilities.	Clients that do not support OAuth 2.1 with PKCE Vector or semantic CRM search, which the documented backend does not provide
Avoid when	Avoid using a highly privileged WordPress administrator account when lower-privilege credentials can satisfy the workflow.	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	Ecosystem official github:automattic · Publisher source ↗	First-party MCP HubSpot · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Not documented Package: Not documented
Popularity evidence
GitHub stars	186 GitHub stars · checked 2026-10-21	Not documented
Package downloads / 30 days	96,955 package downloads / 30 days · checked 2026-10-21	No reliable download data
Client coverage
Client coverage details	Not documented	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	OAuth 2.1 with PKCE is the preferred path; reviewed alternatives include JWT and WordPress Application Passwords.	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	Open-source proxy; WordPress hosting/plugins/services and AI/model 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.
Permissions	Effective permissions follow the authenticated WordPress user and the abilities exposed by the backend MCP Adapter.	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	WordPress content, metadata and action results can transit the proxy and connected AI client/provider. OAuth tokens are stored locally by the proxy and must be protected.	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	Official WordPress MCP adapter is promising and ecosystem-significant, but self-hosted/plugin-dependent maturity and ability scoping need more evidence.	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	A high-privilege WordPress user can expose broad content/site administration authority to the AI client.	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-10-21	2026-07-24
Candidate evidence	2026-10-21T00:00:00Z	2026-09-24T04:25:05.554391Z

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

Read the evidence method →