Head to head · Company knowledge search · October 2026 research run

Dust vs Microsoft MCP Server for Enterprise

Dust scores 63.2 (B) on agent readiness against Microsoft MCP Server for Enterprise's 54.1 (C), and leads in 4 of 7 scored categories. Microsoft MCP Server for Enterprise leads on security & auth and payments & pricing. Both do company knowledge search.

Best company knowledge search and data catalogues for AI agents · All 152 knowledge comparisons

Which one, for what

Dust B

Best for A team that already works in Dust and wants an outside agent to search its spaces, read documents and call its agents with a user's own access.

Ahead on

  • Schema & documentation, 75 against 29
  • Agent ergonomics, 67 against 55
  • Maintenance & community, 86 against 43

Also in its favour

  • Open source

Watch for

Programmatic usage has no free credits. It draws only on the workspace credit pool, which Free seats cannot use

Microsoft MCP Server for Enterprise C

Best for Admins and support agents who ask questions about users, groups, apps, devices and licences in an Entra tenant.

Ahead on

  • Security & auth, 85 against 75
  • Payments & pricing, 50 against 30

Watch for

An administrator has to provision it per tenant with PowerShell and grant each client

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.

Schema & documentation Dust +46

Dust 75

A public OpenAPI 3.0 document at dust.tt/api/doc, linked from the docs, now with 56 paths and 71 operations (25). llms.txt at docs.dust.tt with a Markdown copy of every page (10). Operation descriptions mostly restate the summary ("Search for nodes in the workspace"), six operations have none, and none says when not to use an endpoint (10 of 20). 44 enums and 277 required markers, though ranges such as the search limit of 1 to 100 sit in the description text and not in the schema (10 of 15). 199 examples, while most error responses are a status and two words ("Bad request") with no body schema (9 of 15). The path carries /api/v1, the document a version (1.0.2), and the product changelog is dated and has carried API deprecation notices. There is no changelog for the API alone (11 of 15).

Microsoft MCP Server for Enterprise 29

The three tools (microsoft_graph_suggest_queries, microsoft_graph_get, microsoft_graph_list_properties) are described in prose on the overview. Their schemas need an Entra tenant to list, so no contract was read (0 of 25). learn.microsoft.com serves Markdown to agents, as for the other Microsoft listings (10). The overview says what each tool does and the workflow they follow, but not when not to use them (12 of 20). Input types weren't readable (0 of 15). A sample prompts page and a Kusto query for its logs, but no documented error responses (7 of 15). No version or changelog found (0). 0 + 10 + 12 + 0 + 7 + 0 = 29.

Maintenance & community Dust +43

Dust 86

The changelog's newest entry is dated 28 October 2026 (30). 78 dated changelog days from 4 August to 28 October 2026 (20). Issues were public on GitHub on 8 October (388 open issues and pull requests by the API's count), with a support email and a community site. On 2 November the dust-tt/dust repository no longer answered a public clone, so issues and reply times are per the 8 October check, not re-read (15 of 25). @dust-tt/client 1.2.9 was published on 22 September 2026, in one language, per the 8 October check (npm unreadable on 2 November). The CLI moved to its own public repository, dust-tt/dust-cli, on 23 October 2026 at version 0.4.6 (12 of 15). The CLI repository runs build and CodeQL workflows with Dependabot. The monorepo's CI and the Node 24.16 requirement are per the 8 October check (9 of 10).

Microsoft MCP Server for Enterprise 43

General availability announced on 17 November 2026 (30). No three dated changes in 90 days were found (0). Questions are answered on Microsoft Q&A, and support goes through Microsoft's channels (8 of 15). The GitHub MCP registry shows an entry under microsoft, seen in a search only, so not counted (0, unchecked). A hosted service with no package to keep current (5 of 10). 30 + 0 + 8 + 0 + 5 = 43.

Payments & pricing Microsoft MCP Server for Enterprise +20

Dust 30

Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public per seat with their credit allowances, but no price per top-up credit was found and the Enterprise programmatic rate is by quote (10). A Free seat has 500 lifetime credits, and the pricing page does not say whether a card is needed. Programmatic usage has no free credits and draws only on the workspace pool, which Free seats cannot use, so the free tier does not cover API calls that run agents (10 of 20). A person signs in through a browser to create a workspace and an admin creates the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Microsoft MCP Server for Enterprise 50

No payment protocol (0). The overview says there's no additional cost or separate licence to enable it, published without a login (30). It's free, but it needs a Microsoft Entra tenant, and some data needs Entra ID P2 or ID Governance licences (20 of 30). An administrator provisions it with PowerShell and grants each client in the tenant (0). 0 + 30 + 20 + 0 = 50.

Agent ergonomics Dust +12

Dust 67

Workspace search takes limit (1 to 100, default 25), and data source search takes top_k and target_document_tokens, so results can be sized. The MCP server's tool list needs a signed-in workspace and was not read (20 of 25). Cursor pagination on search, limit and lastValue on conversations, and tag, parent and timestamp filters on data source search (20). The source returns errors as a type and a message, such as rate_limit_error with the reason a call was blocked, but the docs give no list of error types (12 of 20). No idempotency keys in the OpenAPI document. Document and row upserts by ID can be repeated safely, and MCP tool annotations were not seen (6 of 20). Search needs only a query. One official SDK language, JavaScript, plus a CLI with a non-interactive mode that prints JSON (9 of 15).

Microsoft MCP Server for Enterprise 55

Three tools, a search over Graph examples, a read-only Graph call and an entity-schema lookup, so a small list, sizes not read (20 of 25). Graph's own query options pass through microsoft_graph_get, but no page or size control is documented for the server (10 of 20). No documented error codes (5 of 20). Read-only by design, per the overview; annotations not readable (12 of 20). No SDK needed, but provisioning is a PowerShell step per tenant and required parameters weren't readable (8 of 15). 20 + 10 + 5 + 12 + 8 = 55.

Security & auth Microsoft MCP Server for Enterprise +10

Dust 75

API keys go in the Authorization header, can be limited to chosen spaces and capped by spend, and the MCP server takes OAuth with dynamic client registration, client ID metadata documents and a required resource parameter, issuing tokens that work only for MCP (28 of 30). An MCP client works as the signed-in user with that user's spaces only, an admin can switch the server off and restrict redirect URIs, and the API has an endpoint to approve or reject an agent's action. No read-only key type was found (16 of 20). Search returns content from connected sources, and no prompt-injection guidance for API or MCP clients was found in the pages read (3 of 15). Audit logs record user, API key and system actors with SIEM streaming, on the Enterprise plan only (12 of 15). SOC 2 Type II and HIPAA support on the security page, a HackerOne disclosure programme with no bounty stated, CodeQL in the public CI (the CLI repository's CodeQL workflow was read on 2 November), and no security.txt (16 of 20).

Microsoft MCP Server for Enterprise 85

Microsoft Entra delegated OAuth: an administrator registers the server and grants each MCP client its scopes, and the server enforces the user's own privileges and those scopes (30). Read-only Graph calls only (20). It returns directory data, names and attributes that users and admins can edit, with no prompt-injection guidance found (5 of 15). Every request lands in Microsoft Graph activity logs, with a Kusto query to filter the server's app ID (15). Microsoft's security programme and certifications, but microsoft.com's security.txt had expired per the Copilot Studio MCP listing (15 of 20). 30 + 20 + 5 + 15 + 15 = 85.

Score by category

CategoryWeightDustMicrosoft MCP Server for EnterpriseEdge
Reliability16%5353even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7529Dust +46
Agent ergonomics13%6755Dust +12
Security & auth14%7585Microsoft MCP Server for Enterprise +10
Payments & pricing10%3050Microsoft MCP Server for Enterprise +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8643Dust +43
Transparency & trust7%5957Dust +2
Negative events≤1500
TotalB 63.2/100C 54.1/100

Facts side by side

FactDustMicrosoft MCP Server for Enterprise
KindHTTP APIMCP server
VendorPermutation LabsMicrosoft
Hosted endpointhttps://dust.tt/mcphttps://mcp.svc.cloud.microsoft/enterprise
TransportsHTTPStreamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumFree
x402nono
LicenceThe docs give MIT for the platform's source at github.com/dust-tt/dust, which didn't answer a public clone on 2 November 2026. The CLI is MIT in its own repository, dust-tt/dust-cli, since 23 October 2026. The hosted service is sold under Dust's own terms. The npm page gave ISC for @dust-tt/client and MIT for @dust-tt/dust-cli on 8 October 2026Closed service under the Microsoft APIs Terms of Use
Tools exposednone3
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-282026-11-17
Terms last updatedno document linked2025-10-01
Privacy policy last updatedno date given2026-09-01
Customer content may train modelsnot read yetyes
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity1.5k stars, 17k npm/wknone
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Dust

A public OpenAPI document of 71 operations, llms.txt and a remote MCP server that acts with the signed-in user's access. API calls that run agents draw only on a paid workspace credit pool, the terms of service went unread, and the GitHub monorepo the docs give as its MIT source didn't answer a public clone on 2 November 2026.

Microsoft MCP Server for Enterprise

A free, read-only MCP server over a Microsoft Entra tenant's directory, with Entra-scoped access and every call in Graph's activity logs. It needs an administrator to provision it per tenant, and its tool schemas, errors and changelog aren't public.

Before you call either

Dust

  1. Use https://eu.dust.tt for a workspace in the EU region and https://dust.tt otherwise, for both the API and the MCP server
  2. Connect an MCP client by OAuth and send the resource parameter in authorisation and token requests. API keys do not work on the MCP server
  3. Expect HTTP 429 with type rate_limit_error when the credit pool, the programmatic monthly cap or the key's spend cap is exhausted. Retrying will not help
  4. Call GET /api/v1/w/{wId}/search with limit (1 to 100, default 25) and cursor, or a data source view's search with top_k
  5. Keep document upserts under 120 a minute per workspace

Microsoft MCP Server for Enterprise

  1. Connect to https://mcp.svc.cloud.microsoft/enterprise with an Entra token for a client your administrator has granted
  2. Call microsoft_graph_suggest_queries first to find the Graph call, then microsoft_graph_get to run it
  3. Expect only reads; it can't change anything in the tenant
  4. Stay under 100 calls a minute per user

Questions

Which is better for AI agents, Dust or Microsoft MCP Server for Enterprise?

Dust scores 63.2 (B) on agent readiness against Microsoft MCP Server for Enterprise's 54.1 (C), and leads in 4 of 7 scored categories. Microsoft MCP Server for Enterprise leads on security & auth and payments & pricing.

Do Dust and Microsoft MCP Server for Enterprise need an API key?

Dust takes an API key or an OAuth sign-in. Microsoft MCP Server for Enterprise uses an OAuth sign-in.

Can an agent call Dust and Microsoft MCP Server for Enterprise without installing anything?

Yes. Dust has a hosted endpoint at https://dust.tt/mcp and Microsoft MCP Server for Enterprise at https://mcp.svc.cloud.microsoft/enterprise.

Are Dust and Microsoft MCP Server for Enterprise open source?

Dust is open source (The docs give MIT for the platform's source at github.com/dust-tt/dust, which didn't answer a public clone on 2 November 2026. The CLI is MIT in its own repository, dust-tt/dust-cli, since 23 October 2026. The hosted service is sold under Dust's own terms. The npm page gave ISC for `@dust-tt/client` and MIT for `@dust-tt/dust-cli` on 8 October 2026). No open-source release is listed for Microsoft MCP Server for Enterprise.

Other comparisons with Dust or Microsoft MCP Server for Enterprise

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.