Head to head · Crm records · October 2026 research run

Microsoft Dynamics 365 Sales vs folk API + MCP

Microsoft Dynamics 365 Sales scores 69.7 (B) on agent readiness against folk API + MCP's 60.8 (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.

Which one, for what

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

  • Reliability, 65 against 55
  • Agent ergonomics, 86 against 70
  • Security & auth, 74 against 43
  • 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

Good 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, 30 against 25
  • Transparency & trust, 81 against 75

Also in its favour

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

Watch for

MCP server in open beta since 1 July 2026

Score by category

CategoryWeight this runMicrosoft Dynamics 365 Salesfolk API + MCPEdge
Reliability16%206555Microsoft Dynamics 365 Sales +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28191folk API + MCP +10
Agent ergonomics13%16.28670Microsoft Dynamics 365 Sales +16
Security & auth14%17.57443Microsoft Dynamics 365 Sales +31
Payments & pricing10%12.52530folk API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87960Microsoft Dynamics 365 Sales +19
Transparency & trust7%8.87581folk API + MCP +6
Negative events≤1500
Total69.7 · B60.8 · C

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 exposed1538
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-10-072026-09-15
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 reviewsnone3.5/5 (2)

Verdicts

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.

folk API + MCP

Dated API versions, a year's support and 6 months' deprecation notice with Deprecation and Sunset headers. MCP server in open beta since 1 July 2026.

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 until details.retryAfter, and remember all your keys share one 600-a-minute budget
  4. Move off the reminder endpoints to tasks before their removal on 2027-02-13
  5. Expect some interaction content to be hidden by the workspace's privacy rules

Questions

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

Microsoft Dynamics 365 Sales scores 69.7 (B) on agent readiness against folk API + MCP's 60.8 (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.