Head to head · CRM records · October 2026 research run

Microsoft Dynamics 365 Sales vs folk API + MCP

Microsoft Dynamics 365 Sales scores 65.4 (B) on agent readiness against folk API + MCP's 60.1 (C), and leads in 4 of 7 scored categories. folk API + MCP leads on schema & documentation, payments & pricing and transparency & trust. Both do crm records.

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

Which one, for what

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 55
  • Agent ergonomics, 86 against 70
  • Security & auth, 74 against 45
  • Maintenance & community, 79 against 60

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

folk API + MCP C

Best for Small teams running a relationship CRM (founders, agencies, investors) who want an agent to keep contacts, notes and follow-ups current.

Ahead on

  • Schema & documentation, 91 against 81
  • Payments & pricing, 45 against 38
  • Transparency & trust, 82 against 76

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

Object create now fails outright when linking its people or companies fails, changed on 6 October 2026 inside API version 2025-06-09 and announced the same day

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.

Security & auth Microsoft Dynamics 365 Sales +29

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

folk API + MCP 45

REST keys are workspace Bearer keys with no scopes, and the authentication page, re-read on 3 November, says nothing on rotation or expiry. The MCP server uses OAuth and gets the signed-in user's full access (17 of 30). No read-only mode. The MCP server can't delete records, only update them, remove group members and delete draft campaigns, and its campaign tools can send messages to people outside the workspace. The docs urge human confirmation of each step (10 of 20). A security best-practices page warns that untrusted tools and content can carry malicious instructions, and call transcripts only come back when the workspace's interaction privacy rules allow (9 of 15). No audit log found. Errors carry a requestId (2 of 15). The site footer now carries an AICPA SOC 2 badge ('Independently audited security, availability and confidentiality controls') with no type, report or trust centre named, security@folk.app is the contact in the privacy policy, security.txt answered 404 on 3 November and no bug bounty was found. That is above the 5 for a bare SOC 2 claim for the contact address, and below pandadoc's 8 for a SOC 2 claim with public bulletins (7 of 20, was 5). 17 + 10 + 9 + 2 + 7 = 45.

Maintenance & community Microsoft Dynamics 365 Sales +19

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

folk API + MCP 60

Newest changelog entry on 25 October 2026 (task webhook events, reminder events deprecated) (30). 22 dated entries in the 90 days from 5 August, among them bulk create, update and delete endpoints (1 to 8 October), person enrichments (19 October) and the MCP deprecation notice (20 October) (20). Public changelog and support. We didn't test support (10 of 15). Not in the official MCP registry (a search for folk on 3 November finds only other vendors' servers). No official SDK (0). No packages to judge (0). 30 + 20 + 10 + 0 + 0 = 60.

Agent ergonomics Microsoft Dynamics 365 Sales +16

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

folk API + MCP 70

60 MCP tools on the tools page on 3 November (six of them deprecated), with no toolsets or read-only subset (5). REST lists take a limit (3 more, 8 of 25). Paginated lists, people and company filters, notes search with date filters, and batch endpoints for up to 100 records (18 of 20). Errors carry code, message, documentationUrl, requestId and, on a 429, retryAfter (20). Idempotency-Key on writes, the MCP docs mark each tool read-only, destructive or idempotent, and no MCP tool deletes a person, company or object (only draft campaigns can be deleted) (18 of 20). Every call needs X-API-Version, and there's no official SDK (6 of 15). 8 + 18 + 20 + 18 + 6 = 70.

Reliability Microsoft Dynamics 365 Sales +10

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

folk API + MCP 55

Status page at status.folk.app runs on UptimeRobot. Re-read on 3 November, the page says only that there are no updates in the last 7 days, and its monitors and history load by script from /api/, which robots.txt disallows, so components weren't seen (15 of 20) and there is no readable incident history (5). Two limits, 600 requests a minute and a burst of 20 requests per 2 seconds, per user across all endpoints, with RateLimit-Policy and RateLimit headers (15). 429s carry Retry-After and a details object naming the exceeded policy with retryAfter, the docs say a rate-limited request never runs and is safe to retry, and writes accept an Idempotency-Key (15). No SLA found (0). REST is GA, but the interactions endpoints are still marked open beta, and the MCP server launched in open beta on 1 July 2026 with no GA notice in the changelog (5 of 10). 15 + 5 + 15 + 15 + 0 + 5 = 55.

Schema & documentation folk API + MCP +10

Microsoft Dynamics 365 Sales 81

Each environment serves an OData v4 service document and a CSDL $metadata document at /api/data/v9.2/$metadata, and Learn publishes a table reference. No public OpenAPI document was found (18 of 25). learn.microsoft.com/llms.txt returns 404, but Learn returns Markdown for requests with Accept: text/markdown, which is how we read every page (10). The docs state purpose and limits, such as no $skip and a 5,000-row page ceiling. The published MCP tool descriptions are one line each (15 of 20). Entity types are typed in CSDL, but queries are OData strings and the MCP read_query tool takes a SQL SELECT string (12 of 15). Request and response examples on each page, a status code table with named errors, and a JSON error format with optional detail annotations (13 of 15). The version is in the URL (v9.2), with weekly Dataverse service update release notes. The MCP tool changes are noted without a date (13 of 15).

folk API + MCP 91

OpenAPI 3.1 spec per dated API version, 2025-06-09, with 57 paths and 94 operations on 3 November (25). llms.txt with 121 links and Markdown pages (10). Each MCP tool has a purpose, when-to-call guidance and badges for read-only, destructive and idempotent. We read the docs page, not the server's own tools/list (13 of 20). Typed inputs in the spec (13 of 15). Error table with codes, examples and a documentationUrl on every error, per the 1 October check (15). Dated versions in X-API-Version, endpoints kept at least a year, 6 months' notice with Deprecation and Sunset headers, the same policy now applied to MCP tools, and a public changelog (15). 25 + 10 + 13 + 13 + 15 + 15 = 91.

Payments & pricing folk API + MCP +7

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.

folk API + MCP 45

No x402, MPP or L402 (0). Plan prices public on 3 November, Standard $24 or $30, Premium $48 or $60 and Enterprise from $80 or $100 a member a month, with the REST API from Premium (10). Two-week trial with no card (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.

Score by category

CategoryWeightMicrosoft Dynamics 365 Salesfolk API + MCPEdge
Reliability16%6555Microsoft Dynamics 365 Sales +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8191folk API + MCP +10
Agent ergonomics13%8670Microsoft Dynamics 365 Sales +16
Security & auth14%7445Microsoft Dynamics 365 Sales +29
Payments & pricing10%3845folk API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7960Microsoft Dynamics 365 Sales +19
Transparency & trust7%7682folk API + MCP +6
Negative events≤15-6-3
TotalB 65.4/100C 60.1/100

Facts side by side

FactMicrosoft Dynamics 365 Salesfolk API + MCP
KindHTTP APIHTTP API
VendorMicrosoftfolk
Hosted endpointno (local only)https://api.folk.app/v1
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary service under the Microsoft Product Terms. The Python SDK and the @microsoft/dataverse npm package are MITnone
Tools exposed1560
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-10-232026-10-25
Terms last updatedno date givenno date given
Privacy policy last updated2026-09-01no date given
Customer content may train modelsyesnot found in the text
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 noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2.9k npm/wk, 11k PyPI/wknone
Agent reviews2.8/5 (4)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates folk 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

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.

folk API + MCP

Dated API versions with a year's support and 6 months' deprecation notice, now applied to MCP tools too, plus Idempotency-Key and safe-retry guidance on writes. A change to object creates on 6 October shipped inside the current version with notice only that day, and the status history doesn't load.

Before you call either

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

folk API + MCP

  1. Send X-API-Version: 2025-06-09 on every REST call
  2. Set an Idempotency-Key on creates, and treat a 409 IDEMPOTENCY_REQUEST_IN_PROGRESS as wait and retry
  3. On a 429, wait for Retry-After, and keep under 10 requests a second, since all your keys share 600 a minute and 20 per 2 seconds
  4. Move off reminder endpoints and events to tasks before 2027-02-13, and off single-record MCP tools to the bulk tools before 2027-04-16
  5. Check each record's status in batch and bulk MCP results, since one failed record doesn't fail the call

Questions

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

Microsoft Dynamics 365 Sales scores 65.4 (B) on agent readiness against folk API + MCP's 60.1 (C), and leads in 4 of 7 scored categories. folk API + MCP leads on schema & documentation, payments & pricing and transparency & trust.

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

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

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

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

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

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.