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 fieldZoho CRM MCPWatchlist candidateintercomMCP100 Selected
Task fit
Best for
  • CRM record and workflow operations in Zoho CRM.
  • Customer-support investigation and knowledge workflows in Intercom.
Not ideal for
  • Production use before the documented maturity gaps are resolved
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

Zoho · Publisher source ↗

First-party MCP

ecosystem:intercom · 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 CodeStreamable HTTP
Claude DesktopStreamable HTTP
CodexStreamable HTTP
VS CodeStreamable HTTP
CursorStreamable HTTP
OpenCodeStreamable HTTP
Claude CodeStreamable HTTP
Claude DesktopStreamable HTTP
CodexStreamable HTTP
VS CodeStreamable HTTP
CursorStreamable HTTP
OpenCodeStreamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe generated hosted endpoints use Zoho OAuth.The hosted endpoint supports Intercom OAuth and bearer-token authentication.
CostThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsZoho CRM roles, profiles, OAuth scopes, endpoint permissions, and audit controls govern access.Intercom workspace permissions and documented OAuth or bearer-token scopes constrain 13 published tools.
Data handlingAuthorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive crm & customer operations information.Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive crm & customer operations information.
Limitations
Tradeoffs
  • The product rollout remains phased, so availability and operating evidence are still developing.
  • Availability is limited to US-hosted workspaces, and support conversations can contain personal data.
Risk contextThe product rollout remains phased, so availability and operating evidence are still developing. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.Availability is limited to US-hosted workspaces, and support conversations can contain personal data. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-07-302026-07-30
Candidate evidence2026-07-30T19:00:00.000Z2026-07-30T19:00:00.000Z

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

Read the evidence method →