Get an audit

Head to head · CRM records · October 2026 research run

Close API + MCP vs SugarAI (SugarCRM)

Close API + MCP scores 66.7 (B) on agent readiness against SugarAI (SugarCRM)'s 49.5 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on agent ergonomics. Both do crm records.

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

Close API + MCPClose · HTTP API B66.7/100#277 of 950 SugarAI (SugarCRM)SugarAI Software Inc. · HTTP API D49.5/100#793 of 950

Which one, for what

Close API + MCP B

Good 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.

Ahead on

  • Reliability, 81 against 61
  • Schema & documentation, 82 against 48
  • Security & auth, 66 against 51
  • Payments & pricing, 30 against 10
  • Maintenance & community, 79 against 22

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

121 MCP tools, and even the read scope loads 71

SugarAI (SugarCRM) D

Good for Companies already running Sugar Sell, Serve or Enterprise that want an agent to read and write records under a named user's roles, and that have Sugar's approval for the integration.

Ahead on

  • Agent ergonomics, 69 against 56

Watch for

The AI Supplemental Terms forbid connecting customer-owned or third-party AI systems, agents or MCP connectors to the Services or APIs except through functionality Sugar has approved. This matters before any probe is run

Score by category

CategoryWeight this runClose API + MCPSugarAI (SugarCRM)Edge
Reliability16%208161Close API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28248Close API + MCP +34
Agent ergonomics13%16.25669SugarAI (SugarCRM) +13
Security & auth14%17.56651Close API + MCP +15
Payments & pricing10%12.53010Close API + MCP +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87922Close API + MCP +57
Transparency & trust7%8.86771SugarAI (SugarCRM) +4
Negative events≤1500
Total66.7 · B49.5 · D

Facts side by side

FactClose API + MCPSugarAI (SugarCRM)
KindHTTP APIHTTP API
VendorCloseSugarAI Software Inc.
Hosted endpointhttps://api.close.com/api/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
LicencenoneProprietary service under the SugarAI Customer Terms of Service
Tools exposed121none
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.close/close-mcpnot listed
Last release2026-09-10none
Terms last updated2025-10-31
Privacy policy last updated2026-05-30no date given
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticeyes
Arbitration or class-action waiveryes
Popularity70 stars, 14k PyPI/wknone
Agent reviews3.5/5 (2)none

Verdicts

Close API + MCP

Three MCP scopes chosen per connection, read (71 tools), safe write (87) and destructive (121). 121 MCP tools, and even the read scope loads 71.

SugarAI (SugarCRM)

The REST reference covers 350 endpoint pages with filters, field selection, bulk calls and upsert by sync_key. SugarAI's AI Supplemental Terms forbid connecting a customer's or third party's AI agent or MCP connector to the APIs unless Sugar has approved it, tokens carry no scopes, and no OpenAPI file, trial or SLA 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

SugarAI (SugarCRM)

  1. Confirm that Sugar has approved the agent integration before connecting. The AI Supplemental Terms forbid unapproved AI agents and MCP connectors on the APIs
  2. POST to /rest/v11_27/oauth2/token with grant_type password and a platform other than base, mobile or portal, or the login can end the user's own session
  3. Send the access token in the OAuth-Token header. It lasts 60 minutes by default, so store the refresh token and not the password
  4. Stay under 20 requests a second on SugarCloud and reuse one session for batches. Over-limit traffic is blocked by IP address until support lifts it
  5. Page with max_num and offset until next_offset is -1, and pass fields to keep responses small
  6. Use PATCH /integrate/:module/:sync_key_field_name/:sync_key_field_value for writes that may be retried, since it inserts or updates by sync_key

Questions

Which is better for AI agents, Close API + MCP or SugarAI (SugarCRM)?

Close API + MCP scores 66.7 (B) on agent readiness against SugarAI (SugarCRM)'s 49.5 (D), and leads in 5 of 7 scored categories. SugarAI (SugarCRM) leads on agent ergonomics.

Do Close API + MCP and SugarAI (SugarCRM) need an API key?

Close API + MCP takes an API key or an OAuth sign-in. SugarAI (SugarCRM) uses an OAuth sign-in.

Can an agent call Close API + MCP and SugarAI (SugarCRM) without installing anything?

Close API + MCP has a hosted endpoint at https://api.close.com/api/v1. No hosted endpoint is listed for SugarAI (SugarCRM).

Other comparisons with Close API + MCP or SugarAI (SugarCRM)

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.

Get an auditSee a sample report