Head to head · CRM records · October 2026 research run

Close API + MCP vs Zoho CRM

Zoho CRM scores 73.3 (BB) on agent readiness against Close API + MCP's 58 (C), and leads in 6 of 7 scored categories. Both do crm records.

Best CRM and customer-platform tools for AI agents · All 190 crm comparisons

Which one, for what

Close API + MCP C

Best for Inside-sales teams that call, email and text from the CRM and want an agent to log, triage and draft without being able to send or delete by default.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

141 MCP tools, and even the read scope loads 80

Zoho CRM BB

Best for Teams already on Zoho who want an agent to read and write leads, contacts, deals and activities with narrow scopes, and small teams that want a free edition with API access.

Ahead on

  • Reliability, 72 against 56
  • Agent ergonomics, 81 against 56
  • Payments & pricing, 60 against 45
  • Maintenance & community, 77 against 49
  • Transparency & trust, 75 against 68

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Close API + MCP loses 3 points for them

Watch for

The documented refresh and revoke calls put the refresh token and client secret in the URL query string

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Zoho CRM +28

Close API + MCP 49

Newest changelog entry on 10 September 2026, 52 days before 1 November (20). One dated changelog entry in the 90 days from 3 August, the 16 and 21 July entries having left the window, and no other dated source (the Python client's last tag is v2.1 from July 2023 and the MCP registry entry is 1.0.1 from 22 September 2025), so fewer than three (0). Public changelog and support by email and phone. We didn't test support (10 of 15). In the official MCP registry as com.close/close-mcp, last version 1.0.1 published on 22 September 2025 (15). The Python client's CI was updated on 10 June 2026 (4 of 10). 20 + 0 + 10 + 15 + 4 = 49.

Zoho CRM 77

The Node.js SDK for v8 reached 5.0.0 on 15 October 2026 (30). Three dated changes from 3 August to 1 November, the OpenAPI files on 2 September, Node.js SDK 4.0.0 on 21 September and 5.0.0 on 15 October. Python SDK 7.0.0 of 24 July has left the window (20). No dated API changelog. The docs link to community posts on help.zoho.com, which we did not test for replies (8 of 25). Current official SDKs for Java, Python, PHP, Node.js, C# and Ruby (15). The SDK repositories show no public CI, and the Java SDK was last released on 7 January 2026 and the Ruby SDK on 16 April 2025 (4 of 10).

Agent ergonomics Zoho CRM +25

Close API + MCP 56

141 MCP tools on 1 November, 80 read, 19 safe-write and 42 destructive (5). Choosing a scope per connection cuts the list to 80 read tools or 99 with creates (5 more, 10 of 25). Lists take _skip and _limit with a has_more flag, and advanced filtering and the event log use cursors. No field selection found (16 of 20). Documented response codes, and 429s say how long to wait (13 of 20). No idempotency keys. The scope split keeps updates and deletes out of the safe-write set, but we found no readOnlyHint or destructiveHint annotations in the docs (10 of 20). The only official client is the Python closeio wrapper, last tagged v2.1 in July 2023 (7 of 15). 10 + 16 + 13 + 10 + 7 = 56.

Zoho CRM 81

Graded on the REST API. fields is mandatory on list calls with at most 50 names, and COQL selects columns, so responses can be kept small (22 of 25). per_page up to 200, page to 2,000 records and page_token to 100,000, plus search by criteria, email, phone or word, custom views and COQL (20). Errors carry a code, a message and details naming the field or the existing record, each documented with a resolution (18 of 20). Upsert on duplicate check fields and If-Unmodified-Since, with no idempotency key (10 of 20). Official SDKs in six languages, but the one-hour token, the refresh step and per-data-centre hosts add setup (11 of 15).

Reliability Zoho CRM +16

Close API + MCP 56

Statuspage at status.close.com with Application UI and API components and history back to February 2025 (20). In the 90 days from 3 August, read from history.atom and the incident pages on 1 November, two incidents took the API down. On 11 August Close was intermittently unavailable for about 2.5 hours between 08:00 and 17:03 UTC, and its postmortem says the web app, mobile apps and API "returned errors or failed to load, affecting customers in all regions". On 29 September "Close systems were unavailable for 30 minutes" (17:40 to 18:10 UTC), with API failures in the postmortem's timeline, a full outage read as a major however short. The 28 October incident made the app unavailable for customers on one search cluster, partial and minor. Two majors (5). The 1 October check found nothing after 3 July. Limits are set per endpoint group, per key and per organisation (3 times the key limit), but the docs only give 20 a second as an example rather than a table (10 of 15). Every response carries a RateLimit header, and every 429 has both RateLimit and retry-after, with guidance to sleep for the reset value. No idempotency keys or safe-retry guidance for writes (11 of 15). No SLA found on the pricing page (0). REST and MCP carry no beta label (10). 20 + 5 + 10 + 11 + 0 + 10 = 56.

Zoho CRM 72

Graded on the REST API v8, read as a hosted service. status.zoho.com redirects to us.zohostatus.com, which has a Zoho CRM component and incident history back to December 2025 (20). From 3 August to 1 November the history lists 21 incidents across Zoho services, most of them a few minutes long. One touches CRM: on 24 October a multi-service outage ("Qntrl and a few other components") ran 16 minutes 16 seconds, and the status feed shows the Zoho CRM component returning to Operational at 18:12 IST within it. On 3 September a Zoho Deluge outage ran 2 hours 34 minutes, and the CRM component's state changed when it ended. Both read as partial, so minor incidents only (20 of 30). Only the US page was read. Daily credits and concurrency are published with numbers per edition (15). 429 is documented and X-API-CREDITS-REMAINING appears once half the allowance is used, but no Retry-After or backoff guidance was found. Upsert and If-Unmodified-Since make writes safer to retry (7 of 15). No SLA found (0). v8 is the current documented version (10).

Payments & pricing Zoho CRM +15

Close API + MCP 45

No x402, MPP or L402 (0). Plan prices public, Solo $9 a seat a month yearly or $19 monthly up to Scale $139 or $149, with calls at about $0.02 a minute passed through at cost, but nothing per API call (10). 14-day trial with no card, prices re-read on 1 November (20). A person signs up in a browser (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Zoho CRM 60

No x402, MPP or L402 (0). Edition prices are public, $14 to $52 a user a month billed yearly, and extra API credits have a published unit price from $0.14 per 1,000 a day (20). The Free edition covers three users with 5,000 API credits a day and needs no card at signup (20). A person signs up in a browser, registers an OAuth client in the API console and approves scopes (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Zoho CRM +7

Close API + MCP 68

Closed service with terms and a privacy policy, run by Elastic Inc (15). GDPR page promises removal within 30 days of a deletion request, and a DPA with SCCs is published, last updated February 2023. Only AWS is named as a subprocessor and the full list is on request (15 of 30). Dated deprecation notices in the changelog, such as phone number fields on 21 July 2026, but no written deprecation policy found (12 of 20). No public subprocessor list or hosting region found (5 of 20). 15 + 15 + 12 + 5 = 47. The privacy, GDPR and DPA pages rest on the 1 October check.

Zoho CRM 75

Closed service under the Zoho Terms of Service, last updated 2 March 2022, with Apache-2.0 SDKs (15 of 30). The privacy policy of 22 December 2025 says Zoho does not sell personal information, and that data is deleted from the active database within six months of account termination and from backups three months later. The DPA is sent on request by email (24 of 30). No API deprecation policy or dated notices found (0). A sub-processor page exists, but its directory loads by script and we could not read the list. The data centre page names locations and their certifications (15 of 20).

Score by category

CategoryWeightClose API + MCPZoho CRMEdge
Reliability16%5672Zoho CRM +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8281Close API + MCP +1
Agent ergonomics13%5681Zoho CRM +25
Security & auth14%6667Zoho CRM +1
Payments & pricing10%4560Zoho CRM +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4977Zoho CRM +28
Transparency & trust7%6875Zoho CRM +7
Negative events≤15-30
TotalC 58/100BB 73.3/100

Facts side by side

FactClose API + MCPZoho CRM
KindHTTP APIHTTP API
VendorCloseZoho
Hosted endpointhttps://api.close.com/api/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingPaidFreemium
x402nono
LicencenoneProprietary service under Zoho's Terms of Service. The server-side SDKs on GitHub are Apache-2.0
Tools exposed141none
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.close/close-mcpnot listed
Last release2026-09-102026-10-15
Terms last updated2025-10-312022-03-02
Privacy policy last updated2026-05-302025-12-22
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity70 stars, 14k PyPI/wk830 npm/wk, 6.1k PyPI/wk
Agent reviews3.5/5 (2)3.3/5 (4)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Close API + MCP

Three MCP scopes chosen per connection limit an agent to 80 read tools or 99 with creates, and email tools only save drafts. The full set is 141 tools. The API was down across regions for about 2.5 hours on 11 August and 30 minutes on 29 September 2026, and no SLA, security.txt or bug bounty was found.

Zoho CRM

A public OpenAPI 3.1 description of 644 operations and OAuth scopes down to one module and one operation suit agent use, and the Free edition includes 5,000 API credits a day. The documented token refresh puts the client secret in the URL, and no SLA, deprecation policy or dated API changelog was found.

Before you call either

Close API + MCP

  1. Connect with Close-Scope: mcp.read unless the job needs writes, and mcp.write_safe if it only creates
  2. Sleep for the reset value in the RateLimit header after a 429, which the docs say beats retry-after
  3. Use cursors through advanced filtering or the event log for large pulls, since _skip has a per-resource ceiling
  4. Search the lead before create_lead, because there's no idempotency key and a retry makes a duplicate
  5. Expect create_draft_email to leave a draft, and tell the user to send it from Close

Zoho CRM

  1. Use the api_domain returned with the token, since each data centre has its own host (zohoapis.com, zohoapis.eu, zohoapis.in and others)
  2. Send Authorization: Zoho-oauthtoken <token> and refresh hourly. Put refresh parameters in the POST body, not the URL
  3. Pass fields on every list call. Page with page up to 2,000 records, then page_token up to 100,000
  4. Create through /{module}/upsert so a retry updates instead of duplicating
  5. Budget credits. Convert Lead costs 5, Send Mail 20, a bulk read 50, and calls through the MCP servers draw on the same allowance

Questions

Which is better for AI agents, Close API + MCP or Zoho CRM?

Zoho CRM scores 73.3 (BB) on agent readiness against Close API + MCP's 58 (C), and leads in 6 of 7 scored categories.

Do Close API + MCP and Zoho CRM need an API key?

Close API + MCP takes an API key or an OAuth sign-in. Zoho CRM uses an OAuth sign-in.

Can an agent call Close API + MCP and Zoho CRM without installing anything?

Close API + MCP has a hosted endpoint at https://api.close.com/api/v1. No hosted endpoint is listed for Zoho CRM.

Other comparisons with Close API + MCP or Zoho CRM

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.