Head to head · CRM records · October 2026 research run

Close API + MCP vs Microsoft Dynamics 365 Sales

Microsoft Dynamics 365 Sales scores 65.4 (B) on agent readiness against Close API + MCP's 58 (C), and leads in 5 of 7 scored categories. Close API + MCP leads on payments & pricing. 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.

Ahead on

  • Payments & pricing, 45 against 38

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.8 out of 5

Watch for

141 MCP tools, and even the read scope loads 80

Microsoft Dynamics 365 Sales B

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

Ahead on

  • Reliability, 65 against 56
  • Agent ergonomics, 86 against 56
  • Security & auth, 74 against 66
  • Maintenance & community, 79 against 49
  • Transparency & trust, 76 against 68

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

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.

Agent ergonomics Microsoft Dynamics 365 Sales +30

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.

Microsoft Dynamics 365 Sales 86

$select, $top and Prefer: odata.maxpagesize size responses. The MCP server has 15 tools, some of them for schema changes and files (22 of 25). $filter, @odata.nextLink paging with pages up to 5,000 rows, and no $skip (20). Errors are JSON with a code and message, a documented status code table and optional annotations with a help link (17 of 20). PATCH on an alternate key upserts, If-Match and If-None-Match limit it to update or create, and ETags give optimistic concurrency. The MCP delete tools are described as running only after explicit user approval. We did not read the live tool list, so readOnlyHint and destructiveHint are unconfirmed (15 of 20). Official SDKs for .NET (Microsoft.PowerPlatform.Dataverse.Client 1.2.27) and Python (PowerPlatform-Dataverse-Client 1.1.0). The docs say Microsoft ships no other language libraries for the Web API (12 of 15).

Maintenance & community Microsoft Dynamics 365 Sales +30

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.

Microsoft Dynamics 365 Sales 79

Dataverse service update 9.2.26103 went to early release on 23 October 2026, with production rollout from 30 October (30). Service updates are weekly, with 9.2.26081 to 9.2.26103 listed from August to October 2026, each with release notes, and Python SDK 1.0.1 (8 September) and 1.1.0 (7 October) and .NET SDK 1.2.27 (4 September) in the window (20). Public release notes and community forums. We did not check how issues on the SDK repositories are answered (10 of 15). Current official SDKs for .NET and Python and the npm MCP proxy @microsoft/dataverse, whose 1.0.81 of 26 September 2026 rests on the 8 October check. The official MCP registry lists only third-party Dataverse and Dynamics servers, per the 8 October check (13 of 15). The Python SDK is marked Production/Stable for Python 3.10 and later and has a python-package workflow, but its runs weren't readable because github.com refused us (6 of 10).

Reliability Microsoft Dynamics 365 Sales +9

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.

Microsoft Dynamics 365 Sales 65

Graded on the Dataverse Web API, with the Dataverse MCP server noted. Service health for a tenant is in the Power Platform and Microsoft 365 admin centres, behind an admin sign-in. The unauthenticated page at status.cloud.microsoft exists, and Microsoft's docs describe it as the place for updates when the admin portals are unavailable. It rendered no components for our reader on 8 October, and on 1 November its robots.txt answered an empty 401, so the host is treated as blocked and wasn't read (10 of 20, a departure from the full 20 because the page with history needs a login). No readable incident history. The Azure status history, which the Azure listings are read from, names no Dynamics 365, Dataverse or Power Platform incident in the 90 days to 1 November and doesn't cover these services (5). Service protection limits are published per user and web server at 6,000 requests and 20 minutes of execution time per five-minute window, and 52 concurrent requests, plus 40,000 requests per licensed user per 24 hours (15). 429 responses carry Retry-After with retry guidance, and upsert on alternate keys with If-Match gives safe retries for writes (15). The SLA for Microsoft Online Services dated 1 October 2026 pays a 25 per cent credit below 99.9 per cent uptime for Sales Enterprise and Professional, per the 8 October check (10). Web API v9.2 and the MCP endpoint /api/mcp are generally available (10).

Security & auth Microsoft Dynamics 365 Sales +8

Close API + MCP 66

REST keys act as one user in one organisation over HTTP Basic and can be deleted. OAuth for apps has only all.full_access plus offline_access, with 1-hour access tokens and a revoke endpoint. The MCP server adds three scopes, mcp.read, mcp.write_safe and mcp.write_destructive, over OAuth with dynamic client registration or a key header (24 of 30). A read-only MCP connection is one header. Safe-write can create but not update or delete. Email tools only make drafts a person sends, and delete tools tell the model to act only on an explicit instruction (18 of 20). The MCP server reads emails, SMS and call transcripts written by outsiders, and we found no injection guidance. Draft-only email closes one exfiltration route (4 of 15). The event log API records changes and is on every plan (12 of 15). SOC 2 Type 2 on the security page. No security.txt (404 on 1 November), and no disclosure policy or bug bounty found (8 of 20). 24 + 18 + 4 + 12 + 8 = 66.

Microsoft Dynamics 365 Sales 74

OAuth 2.0 through Microsoft Entra ID is the only route, with delegated sign-in or an application user holding a client secret or certificate. The OAuth scopes are coarse (user_impersonation, .default, mcp.tools) and the limits come from Dataverse security roles (26 of 30). Security roles set privileges per table and the MCP server follows them and row-level security. Each MCP client app must be allowed per environment by an administrator, and only Copilot Studio is on by default. The delete tools are described as needing explicit user approval, but Microsoft's sample agent instructions on the configuration page tell the agent not to ask before deleting (17 of 20). Lead, contact and email text written by outsiders reaches the model, and the MCP pages we read give no injection guidance (3 of 15). Dataverse auditing logs record changes and user access, readable through the Web API, once an administrator turns it on. It does not cover retrieve operations (13 of 15). SOC 2 Type 2 lists Dynamics 365, per the 8 October check, and security.txt points to MSRC and the bounty policy, but the file's Expires date of 23 September 2026 had still passed on 1 November. MSRC publishes CVEs for service-side flaws in Dynamics 365 and Dataverse. Three Critical ones in the last 12 months name Dynamics 365 (online) or Dataverse and are counted under negative events, and a fourth names only Dynamics 365 without the app (15 of 20).

Transparency & trust Microsoft Dynamics 365 Sales +8

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.

Microsoft Dynamics 365 Sales 76

Closed service under the Microsoft Product Terms for Dynamics 365, with MIT SDKs (15). The privacy statement, last updated September 2026, says customer agreements control for enterprise products and points to the Product Terms and the Data Protection Addendum of 22 May 2026, which we did not read. Its retention wording is general, and its line on using data to train AI models is not reconciled with the enterprise terms in what we read (18 of 30). The Power Platform deprecations page was updated on 28 October 2026 with dated notices, and the Web API docs state how versions stay compatible. The MCP tool removals carry no date (15 of 20). The region is chosen per environment, with an EU Data Boundary. We did not read a subprocessor list (12 of 20).

Payments & pricing Close API + MCP +7

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.

Microsoft Dynamics 365 Sales 38

No x402, MPP or L402 (0). Seat prices are public at $65, $105 and $150 a user a month, paid yearly. MCP calls from agents built outside Copilot Studio are billed in Copilot Credits at published credit counts, and we did not read a dollar price per credit (10). The Dynamics 365 trial page states 30 days free and the Power Apps Developer Plan is a free Dataverse environment with Web API access. Neither page says whether a card is needed (15 of 20). A person registers an app in Entra ID and an administrator creates the application user or allows the MCP client (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Score by category

CategoryWeightClose API + MCPMicrosoft Dynamics 365 SalesEdge
Reliability16%5665Microsoft Dynamics 365 Sales +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8281Close API + MCP +1
Agent ergonomics13%5686Microsoft Dynamics 365 Sales +30
Security & auth14%6674Microsoft Dynamics 365 Sales +8
Payments & pricing10%4538Close API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4979Microsoft Dynamics 365 Sales +30
Transparency & trust7%6876Microsoft Dynamics 365 Sales +8
Negative events≤15-3-6
TotalC 58/100B 65.4/100

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 exposed14115
Read-only variant documentedyesno
llms.txtyesno
MCP registrycom.close/close-mcpnot listed
Last release2026-09-102026-10-23
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)2.8/5 (4)

The panel on both

One of the 2 reviewers who reviewed both rates Close API + MCP higher, the other way from the total score.

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.

Microsoft Dynamics 365 Sales

Dynamics 365 Sales data sits in Dataverse, reached via 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, no public incident history was readable, and Microsoft disclosed three Critical service-side flaws in Dataverse and Dynamics in 2026.

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 65.4 (B) on agent readiness against Close API + MCP's 58 (C), and leads in 5 of 7 scored categories. Close API + MCP leads on 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.