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 fieldHubSpot MCPMCP100 SelectedSlack MCP ServerMCP100 Selected
Task fit
Best for
  • 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
  • Searching approved Slack channels, messages, files, users, and emoji
  • Reading project conversations and threads from an MCP client
  • Drafting or sending messages and managing canvases with explicit user approval
Not ideal for
  • Clients that do not support OAuth 2.1 with PKCE
  • Vector or semantic CRM search, which the documented backend does not provide
  • Bulk Slack export or archival
  • Unattended messaging, channel creation, or canvas modification
Avoid when
  • 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
  • Private channels, direct messages, files, or user profiles cannot be shared with the external AI client
  • Workspace administrators have not approved the Slack app and MCP integration
  • The agent combines untrusted external content with write-capable Slack tools without isolation
Provenance
Provenance details

First-party MCP

HubSpot · Publisher source ↗

First-party MCP

Slack · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
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
AuthenticationOAuth 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.Slack uses confidential OAuth for MCP clients with a registered fixed Slack app ID and client secret. Cursor's publisher-documented integration uses Slack's fixed client ID and opens an OAuth workspace authorization flow.
CostHubSpot 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.Slack documents no separate MCP server fee. Access to history, search, apps, administration, and AI-client capabilities depends on the workspace's Slack plan; standard Slack API rate limits apply.
PermissionsRead 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.Slack maps tools to granular user-token scopes for public/private/DM search, files, channel history, messages, reactions, conversations, canvases, profiles, and member lists. Actions execute on behalf of the authenticated user and remain subject to workspace/app approval, Slack access controls, and IP allowlists.
Data handlingHubSpot'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.Searches, messages, channel history, file content, canvases, user profiles, and tool outputs flow through Slack's managed MCP endpoint to the configured client and its model provider. Slack audit logs can record MCP activity; client-side retention is governed separately.
Limitations
Tradeoffs
  • 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.
  • Granular OAuth scopes allow narrow access, but useful cross-workspace search can still reveal highly sensitive conversations.
  • Slack's managed endpoint avoids a local server, while requiring confidential OAuth, a fixed app ID, and an eligible directory-published or internal app.
  • The server includes both read and write tools and is subject to Slack Web API rate limits.
Risk contextCRM 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.Slack may contain private messages, credentials, customer data, files, and regulated communications. Request only required OAuth scopes, use an approved app, review the client/model retention policy, isolate other untrusted MCP sources, audit activity, and confirm every send/create/update action. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-07-29T20:58:26.000Z2026-07-29T20:58:26.000Z

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

Read the evidence method →