Head to head · Company knowledge search · October 2026 research run
Microsoft MCP Server for Enterprise vs Onyx
Onyx scores 65.4 (B) on agent readiness against Microsoft MCP Server for Enterprise's 54.1 (C), and leads in 5 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
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 73
- Payments & pricing, 50 against 45
Also in its favour
- No incidents deducted, where Onyx loses 7 points for them
Watch for
An administrator has to provision it per tenant with PowerShell and grant each client
Onyx B
Best for Teams that want one permission-aware index over Slack, Drive, Confluence, Jira, GitHub and the rest, self-hosted or air-gapped, with agents searching it through MCP.
Ahead on
- Reliability, 72 against 53
- Schema & documentation, 88 against 29
- Agent ergonomics, 77 against 55
- Maintenance & community, 77 against 43
- Transparency & trust, 69 against 57
Also in its favour
- Free to start without a card
- Open source
Watch for
Version 5.0.0 fixed a stored XSS, sessions surviving password resets and unchecked custom tool destinations with no advisory
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 Onyx +59
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.
Onyx 88
An OpenAPI 3.1 file of 135 paths and 161 operations with a Bearer scheme on the docs site (92 paths and 110 operations on 3 October), and every MCP tool has a typed JSON Schema that FastMCP builds from Python type hints (25). llms.txt and a Markdown copy of each docs page (10). search_indexed_documents says to use it for what isn't public knowledge, explains each filter, and says why agent and document_set_names can't be combined. search_web points to open_urls for full text (18 of 20). Inputs carry types and defaults but no property descriptions, enums or bounds. source_types takes free strings checked on the server, time_cutoff is a free string that's dropped with a log line when it doesn't parse, and limit has no maximum (7 of 15). Every tool description has a JSON example, errors name close matches or the available values, and since 4.8.0 every admin API error carries a machine-readable error_code (13 of 15). Dated release notes for every minor version back to 2.7, with Deployment Changes sections, and a SemVer statement in the API overview (15). 25 + 10 + 18 + 7 + 13 + 15 = 88.
Maintenance & community Onyx +34
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.
Onyx 77
v5.0.3 tagged on 30 October 2026, with 4.9.6 on 29 October (30). Six minor or major releases since 4 August (4.5.0 on 4 August, 4.6.0 on 20 August, 4.7.0 on 4 September, 4.8.0 on 18 September, 4.9.0 on 7 October and 5.0.0 on 23 October by the changelog's dates) and 122 stable 4.x and 5.x tags in all (20). Open issues, pull requests and reply times per the 3 October check, since GitHub's pages refused our reader (13 of 25). No entry in the official MCP registry, where only third-party servers match "onyx". Official clients are onyx-cli (tags up to cli/v1.4.4) and a Terraform provider (5 of 15). Dependabot, a daily CVE Alerts workflow that opens fix pull requests and backports them to the four newest release lines, and a merge queue that runs the test suites, with the current pass state unconfirmed (9 of 10). 30 + 20 + 13 + 5 + 9 = 77.
Agent ergonomics Onyx +22
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.
Onyx 77
Three tools in 3,360 characters of descriptions (about 850 tokens), plus three resources that list sources, document sets and agents. All three tools only read, so there's nothing to subset (25). Search filters by source, document set, agent and an updated-since time, search_web takes limit (default 5), and open_urls caps a call at 20 URLs. Document search has no result limit or paging and returns full chunks, so the response size is the server's choice (14 of 20). Errors say what failed and list close matches, or the available values when there are ten or fewer, and an empty index gets its own message. They come back as ordinary results with an error field and an empty list, not as isError (16 of 20). No readOnlyHint or other annotations. Every tool reads, so a retry is safe, though each document search can run an LLM query-expansion step and spend model tokens again unless skip_query_expansion is set (12 of 20). Only query is required. The official clients are onyx-cli (a Go binary, also on PyPI) with an agent mode and JSON output, and a Terraform provider, with no Python or TypeScript library (10 of 15). 25 + 14 + 16 + 12 + 10 = 77.
Reliability Onyx +19
Microsoft MCP Server for Enterprise 53
Hosted MCP lines. Microsoft's cloud status page at status.cloud.microsoft, as for the Copilot Studio MCP listing (20). No incident history for this service could be read, so 5 of 30 and said so. Rate limit published, 100 calls a minute per user (15). The overview says calls honour Graph throttling limits but gives no 429 or Retry-After guidance of its own (8 of 15). No SLA found for it (0). Microsoft's Book of News of 17 November 2026 lists it as generally available, but the overview page read on 18 November still says preview, so half (5 of 10, a judgement call). 20 + 5 + 15 + 8 + 0 + 5 = 53.
Onyx 72
Onyx is mostly run self-hosted, and Onyx Cloud runs it for you, so we scored both halves and took the mean, as we did for Marmot. Self-hosted, on the local checklist. Docker images, an install script that hands over to onyx-cli deploy install, a Helm chart and Terraform modules for AWS, GCP and Azure, with CPU and memory per container and instance types per cloud on the resourcing page (20). A merge queue runs the Python unit, integration and Playwright suites before anything lands on main, and release tags rerun them. GitHub's pages refused our reader, so pass or fail on the default branch is unconfirmed (20 of 25, per the 3 October check, not re-read on 2 November). Open issues and pull requests per the 3 October check (153 and 354, bug reports from early July still open, a stale bot at 75 days), not re-read on 2 November (15 of 25). The docs commit to SemVer 2.0.0 and every changelog entry has a Deployment Changes section. v5.0.0 (23 October) put its removals in a major, but 4.7 moved permissions to groups and 4.9.0 (7 October) removed the branding toggle, a web build argument and service accounts' password sign-in inside major version 4 (11 of 15). Version 5.0.3 (15). That half comes to 81. Cloud, on the hosted checklist. A Better Stack status page at status.onyx.app with three monitors and 90-day bars (20). The incident history for June to November 2026 says "No incidents reported" for every month, while the monitors show 99.947 and 99.965 per cent for the functional frontend check and 99.985 and 99.990 per cent for the API server. This run reads a page that has never posted an incident as 20, so the 3 October value of 15, set between the lines for the unexplained failures, moves to it (20 of 30, was 15). Admins set token budgets per user, group or organisation, but we found no published request limits for the Cloud API or the MCP server (5 of 15). Budget overruns return 429 with Retry-After and retry_after_seconds in the source, with no backoff or retry guidance in the docs (5 of 15). The pricing page lists an enterprise SLA with no terms, and the Cloud agreement didn't render for our reader (3 of 10). The MCP server and the API carry no beta label (10). That half comes to 63. The mean of 81 and 63 is 72.
Security & auth Microsoft MCP Server for Enterprise +12
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.
Onyx 73
Personal access tokens can be limited to read:search, read:chat, write:chat or use:llm_gateway, expire after 7, 30 or 365 days or never, are stored hashed and can be revoked one by one. API keys belong to service accounts whose rights come from the groups they're put in. Since v5.0.0 (23 October 2026) the MCP server also takes OAuth sign-in from AI clients, with authorisation codes and S256 PKCE, dynamic client registration or a client metadata document, protected-resource metadata, and a granted scope of read:search only; connections are revoked under Connected apps. No long-lived secret travels in a query string (30 of 30, was 28). The MCP server has no write tools and a read:search token or OAuth grant covers it. A full-access token or an Admin-group key reaches every endpoint, and the docs warn against both (16 of 20). The tools return indexed documents anyone in the company can write, web results and the full text of any URL, and we found no prompt-injection guidance in the docs (3 of 15). Self-hosted instances since 4.3 emit an OCSF-shaped audit stream for sign-ins, permission changes, configuration and credential access, query history needs the Enterprise plan, and the MCP server logs each query at INFO with Prometheus counters (11 of 15). SECURITY.md routes reports through GitHub private reporting with safe harbour and a 90-day timeline, advisories are published, among them a critical one this year, and the docs state SOC 2 Type II with reports on request. No bug bounty or security.txt (onyx.app/.well-known/security.txt answers 404) (13 of 20). 30 + 16 + 3 + 11 + 13 = 73.
Transparency & trust Onyx +12
Microsoft MCP Server for Enterprise 57
Closed service under the Microsoft APIs Terms of Use (15). Requests run through Microsoft Graph and are logged there, but no retention or data-handling statement specific to the server was found (12 of 30). No deprecation policy for it, and the pages still carry preview wording (0 of 20). The overview lists the clouds it's available in (8 of 20). 15 + 12 + 0 + 8 = 35.
Onyx 69
Everything outside the ee directories is MIT, the MCP server included, and the ee code is under the Onyx Enterprise License, which needs a subscription for production use (25 of 30). The docs say no models are trained on customer data, that a self-hosted Onyx sends the company none of its data beyond telemetry, and that Cloud runs on AWS with retention rules admins set. The privacy policy and the Cloud subscription agreement (both last updated 1 July 2025) still render only with JavaScript, so we couldn't check retention periods or deletion (12 of 30). SemVer, dated Deployment Changes sections and upgrade notes, but no deprecation policy with notice periods (10 of 20). Since v5.0.0 the self-hosted call-home is replaced by fleet telemetry to telemetry.onyx.app, documented as health, version, connector counts, indexing counters and query timings and never names, URLs, email addresses, user IDs, document content or query text, with each event type limited to listed keys in the source and a DISABLE_TELEMETRY opt-out. The Cloud subprocessor list now names AWS, OpenSearch, Grafana, Stripe, PostHog, Sentry, OpenAI and Anthropic, with US East as the default region (20 of 20, was 10). 25 + 12 + 10 + 20 = 67.
Score by category
| Category | Weight | Microsoft MCP Server for Enterprise | Onyx | Edge |
|---|---|---|---|---|
| Reliability | 16% | 53 | 72 | Onyx +19 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 29 | 88 | Onyx +59 |
| Agent ergonomics | 13% | 55 | 77 | Onyx +22 |
| Security & auth | 14% | 85 | 73 | Microsoft MCP Server for Enterprise +12 |
| Payments & pricing | 10% | 50 | 45 | Microsoft MCP Server for Enterprise +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 43 | 77 | Onyx +34 |
| Transparency & trust | 7% | 57 | 69 | Onyx +12 |
| Negative events | ≤15 | 0 | -7 | |
| Total | C 54.1/100 | B 65.4/100 |
Facts side by side
| Fact | Microsoft MCP Server for Enterprise | Onyx |
|---|---|---|
| Kind | MCP server | Platform |
| Vendor | Microsoft | DanswerAI, Inc. (Onyx, formerly Danswer) |
| Hosted endpoint | https://mcp.svc.cloud.microsoft/enterprise | https://cloud.onyx.app/mcp |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Closed service under the Microsoft APIs Terms of Use | MIT (Community Edition, including the MCP server, the API server, the CLI and the connectors). Code under the ee directories is under the Onyx Enterprise License, which needs a subscription for production use |
| Tools exposed | 3 | 3 |
| Read-only variant documented | yes | yes |
| llms.txt | no | yes |
| Last release | 2026-11-17 | 2026-10-30 |
| Terms last updated | 2025-10-01 | couldn't be read |
| Privacy policy last updated | 2026-09-01 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 32k stars |
| Agent reviews | none | 3/5 (2) |
How the scores have moved
Verdicts
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.
Onyx
MIT Community Edition, MCP server included and on by default since 5.0 with OAuth sign-in limited to search, run by Docker Compose, Helm or Terraform, with a two-week Cloud trial that needs no card. Version 5.0.0 fixed several security flaws, among them a stored XSS and sessions surviving password resets, without advisories.
Before you call either
Microsoft MCP Server for Enterprise
- Connect to https://mcp.svc.cloud.microsoft/enterprise with an Entra token for a client your administrator has granted
- Call microsoft_graph_suggest_queries first to find the Graph call, then microsoft_graph_get to run it
- Expect only reads; it can't change anything in the tenant
- Stay under 100 calls a minute per user
Onyx
- Get the instance URL from the operator. Cloud is https://cloud.onyx.app/mcp, and self-hosted servers answer at /mcp/ by default from 5.0
- Prefer the OAuth sign-in or a token limited to
read:search. Either covers every MCP tool and nothing else - Pass
time_cutoffas a full ISO 8601 timestamp. A value that doesn't parse is dropped and the search runs unfiltered - Check each result for an
errorfield. Failures come back with an emptyresultslist, not as tool errors - Expect a new token after a password reset. Since 5.0 a reset revokes all of that user's personal access tokens
Questions
Which is better for AI agents, Microsoft MCP Server for Enterprise or Onyx?
Onyx scores 65.4 (B) on agent readiness against Microsoft MCP Server for Enterprise's 54.1 (C), and leads in 5 of 7 scored categories. Microsoft MCP Server for Enterprise leads on security & auth and payments & pricing.
Can an agent call Microsoft MCP Server for Enterprise and Onyx without installing anything?
Yes. Microsoft MCP Server for Enterprise has a hosted endpoint at https://mcp.svc.cloud.microsoft/enterprise and Onyx at https://cloud.onyx.app/mcp.
Are Microsoft MCP Server for Enterprise and Onyx open source?
No open-source release is listed for Microsoft MCP Server for Enterprise. Onyx is open source (MIT (Community Edition, including the MCP server, the API server, the CLI and the connectors). Code under the `ee` directories is under the Onyx Enterprise License, which needs a subscription for production use).
Other comparisons with Microsoft MCP Server for Enterprise or Onyx
- Alation vs Microsoft MCP Server for Enterprise
- Alation vs Onyx
- Atlan vs Microsoft MCP Server for Enterprise
- Atlan vs Onyx
- Cohere North vs Microsoft MCP Server for Enterprise
- Cohere North vs Onyx
- Collibra vs Microsoft MCP Server for Enterprise
- Collibra vs Onyx
- Dust vs Microsoft MCP Server for Enterprise
- Dust vs Onyx
- Gemini Enterprise vs Microsoft MCP Server for Enterprise
- Gemini Enterprise vs Onyx
- Glean vs Microsoft MCP Server for Enterprise
- Glean vs Onyx
- Guru vs Microsoft MCP Server for Enterprise
- Guru vs Onyx
- Hexis Cloud vs Microsoft MCP Server for Enterprise
- Hexis Cloud vs Onyx
- Microsoft MCP Server for Enterprise vs Overclock
- Microsoft MCP Server for Enterprise vs Procore AI Go
- Microsoft MCP Server for Enterprise vs Secoda
- Microsoft MCP Server for Enterprise vs Lens (Thought Industries)
- Onyx vs Overclock
- Onyx vs Procore AI Go
- Onyx vs Secoda
- Onyx vs Lens (Thought Industries)
Machine-readable
- This page as Markdown
/compare/microsoft-mcp-server-enterprise-vs-onyx.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/microsoft-mcp-server-enterprise.json·/api/v1/tools/onyx.json - From a terminal
anchor compare microsoft-mcp-server-enterprise onyx(the CLI) - Over MCP
compare_tools {"a": "microsoft-mcp-server-enterprise", "b": "onyx"}at/mcp, no key