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 candidateSalesforce Hosted MCPMCP100 Selected
Task fit
Best for
  • CRM record and workflow operations in Zoho CRM.
  • Connect compatible AI clients to Salesforce's documented MCP capabilities.
Not ideal for
  • Production use before the documented maturity gaps are resolved
  • Users who need a fully reviewed MCP100 recommendation today
Avoid when
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

First-party MCP

Zoho · Publisher source ↗

First-party MCP

Salesforce · 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
AuthenticationThe generated hosted endpoints use Zoho OAuth.Follow only the publisher source; credential storage, scopes, and revocation remain under review.
CostThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.Publisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion.
PermissionsZoho CRM roles, profiles, OAuth scopes, endpoint permissions, and audit controls govern access.Exact permissions and read/write boundaries have not completed MCP100 review.
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.Candidate-specific retention, subprocess, telemetry, and model-data behavior remain review items.
Limitations
Tradeoffs
  • The product rollout remains phased, so availability and operating evidence are still developing.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
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.Use a test account, least privilege, read-only controls where available, and explicit approval for mutations.
Evidence date
Editorial review2026-07-302026-07-24
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 →