Get an audit

Head to head · Crm records · October 2026 research run

Close API + MCP vs Microsoft Dynamics 365 Sales

Microsoft Dynamics 365 Sales scores 69.7 (B) on agent readiness against Close API + MCP's 66.7 (B), and leads in 3 of 7 scored categories. Close API + MCP leads on reliability and payments & pricing. Both do crm records.

Close API + MCPClose · HTTP API B66.7/100#211 of 629 Microsoft Dynamics 365 SalesMicrosoft · HTTP API B69.7/100#142 of 629

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 65
  • Payments & pricing, 30 against 25

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

Microsoft Dynamics 365 Sales B

Good for Organisations already on Dynamics 365 or Microsoft 365 that want an agent to work inside existing security roles.

Ahead on

  • Agent ergonomics, 86 against 56
  • Security & auth, 74 against 66
  • Transparency & trust, 75 against 67

Also in its favour

  • Runs on your own machine

Watch for

No public OpenAPI document. The contract is an OData CSDL $metadata document served by each environment behind sign-in

Score by category

CategoryWeight this runClose API + MCPMicrosoft Dynamics 365 SalesEdge
Reliability16%208165Close API + MCP +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28281Close API + MCP +1
Agent ergonomics13%16.25686Microsoft Dynamics 365 Sales +30
Security & auth14%17.56674Microsoft Dynamics 365 Sales +8
Payments & pricing10%12.53025Close API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87979even
Transparency & trust7%8.86775Microsoft Dynamics 365 Sales +8
Negative events≤1500
Total66.7 · B69.7 · B

Facts side by side

FactClose API + MCPMicrosoft Dynamics 365 Sales
KindHTTP APIHTTP API
VendorCloseMicrosoft
Hosted endpointhttps://api.close.com/api/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyOAuth
PricingPaidPaid
x402nono
LicencenoneProprietary service under the Microsoft Product Terms. The Python SDK and the @microsoft/dataverse npm package are MIT
Tools exposed12115
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.close/close-mcpnot listed
Last release2026-09-102026-10-07
Terms last updated2025-10-31no date given
Privacy policy last updated2026-05-302026-09-01
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 textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity70 stars, 14k PyPI/wk2.9k npm/wk, 11k PyPI/wk
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.

Microsoft Dynamics 365 Sales

Dynamics 365 Sales data sits in Dataverse, reached through the OData v4 Web API or the Dataverse MCP server with 15 tools. Service protection limits are published and 429 responses carry Retry-After. Access needs an Entra app registration and an administrator, and the public service health page showed no history to our reader.

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

Microsoft Dynamics 365 Sales

  1. Send OData-MaxVersion: 4.0, OData-Version: 4.0 and Accept: application/json, and name columns with $select on every read
  2. Page with Prefer: odata.maxpagesize (up to 5,000) and follow @odata.nextLink. $skip is not supported
  3. On 429, wait the seconds in Retry-After. The x-ms-ratelimit-* headers are for debugging, not pacing
  4. Use PATCH on an alternate key to upsert, and add If-Match: * when an update must not create a record
  5. For MCP, call describe for logical table and column names before read_query. Update any allow list that still names describe_table, list_tables or fetch

Questions

Which is better for AI agents, Close API + MCP or Microsoft Dynamics 365 Sales?

Microsoft Dynamics 365 Sales scores 69.7 (B) on agent readiness against Close API + MCP's 66.7 (B), and leads in 3 of 7 scored categories. Close API + MCP leads on reliability and payments & pricing.

Do Close API + MCP and Microsoft Dynamics 365 Sales need an API key?

Close API + MCP takes an API key or an OAuth sign-in. Microsoft Dynamics 365 Sales uses an OAuth sign-in.

Can an agent call Close API + MCP and Microsoft Dynamics 365 Sales without installing anything?

Close API + MCP has a hosted endpoint at https://api.close.com/api/v1. Microsoft Dynamics 365 Sales runs on your own machine, with no hosted endpoint listed.

Other comparisons with Close API + MCP or Microsoft Dynamics 365 Sales

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