Head to head · Company knowledge search · October 2026 research run
Cohere North vs Microsoft MCP Server for Enterprise
Microsoft MCP Server for Enterprise and Cohere North score within a point of each other on agent readiness, 54.1 (C) and 53.2 (D). Cohere North leads on schema & documentation, agent ergonomics, maintenance & community and transparency & trust. Both do company knowledge search.
Best company knowledge search and data catalogues for AI agents · All 152 knowledge comparisons
Which one, for what
Best for Regulated companies that want an agent and search platform over their own documents, mail and tickets, run privately or air-gapped and called through a REST or OpenAI-compatible API.
Ahead on
- Schema & documentation, 85 against 29
- Agent ergonomics, 71 against 55
- Maintenance & community, 68 against 43
- Transparency & trust, 69 against 57
Watch for
No public price, trial or self-serve signup. Access starts with a sales conversation
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
- Reliability, 53 against 32
- Security & auth, 85 against 77
- Payments & pricing, 50 against 0
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Cohere North loses 4 points for them
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 Cohere North +56
Cohere North 85
Public OpenAPI 3.1 specs for the North API (86 paths, 128 operations) and for Compass (46 paths, 57 operations), with Bearer auth (25). llms.txt per section, a Markdown copy of each page with .md, and a docs MCP server (10). All 128 operations have a summary and 100 have a description, but several descriptions are Python docstrings ("Args: chat_request (NorthChatRequest)"), and when-to-use guidance sits in the guides rather than the spec (12 of 20). 334 enums and typed request bodies. The chat request has 27 properties with only stream required, and documents accepts free strings or objects (12 of 15). The errors page documents the error shape, every error type, field-level validation errors and streaming errors, with curl, Python and TypeScript examples. The spec itself carries no examples (13 of 15). Versioned v1 and v2 paths and a dated platform changelog with releases several times a week, though entries are mostly version numbers and image lists (13 of 15). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation.
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.
Payments & pricing Microsoft MCP Server for Enterprise +50
Cohere North 0
Read with the hosted rubric, since Cohere sells North as a licensed platform whether it hosts it or the customer does. No x402, MPP or L402 (0). cohere.com/pricing says "Get in touch for custom enterprise pricing" for North (0). No North trial or free tier found. Cohere's trial API keys cover the models, not North (0). A person buys through sales, then an admin registers OAuth apps or a user copies a token (0). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
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.
Maintenance & community Cohere North +25
Cohere North 68
North Platform v1.15.4 on 1 October 2026 is the last dated API change recorded, 34 days before the check (20). The North 2 announcement of 5 October isn't shown to change the API. The North changelog had dated entries from 23 June to 1 October 2026, several a week, across parallel 1.12, 1.13, 1.14 and 1.15 release lines, three or more of them since 6 August (20). A closed service with a public dated changelog, a support bundle procedure and a Cohere Discord. Changelog entries are mostly version numbers and container image lists, and we didn't test support (10 of 15). Official SDKs for Python, TypeScript and Go are current with the platform but aren't published to PyPI or npm, and the Go SDK repository isn't public (a clone asks for credentials) (12 of 15). The North MCP Python SDK is at 0.4.5 (16 July 2026) with its last commit on 29 July 2026, and its README installs it over git+ssh (6 of 10). The changelog and docs are per the 5 October check, not re-read on 4 November under Cohere's terms.
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.
Reliability Microsoft MCP Server for Enterprise +21
Cohere North 32
Read with the hosted lines and scored on the Cohere-hosted North API that the quickstart uses (north.cohere.com). Private deployments run on the customer's own infrastructure. status.cohere.com is a public Statuspage, but the 5 October reading of its components came from its JSON API, which this method doesn't read, so it is struck, and the page isn't re-read under Cohere's terms (0). No readable incident history for North itself; the earlier incident reading came from the same JSON API (5). No fixed limits for the North API. Admins set request and token tiers per user and group through Flow Control, which is marked Alpha and needs a Helm setting before it applies (5 of 15). The errors page marks 429 and 503 as the only retryable errors, sends Retry-After and retry_after_seconds, and asks for exponential backoff with jitter capped near 60 seconds. No idempotency or safe-retry guidance for writes (12 of 15). The terms of use sell the service "as is" and "as available", and no North SLA was found (0). Chat, Responses and the agents API carry no beta label (10). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation.
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.
Agent ergonomics Cohere North +16
Cohere North 71
Chat takes max_tokens, citation options, a truncation strategy and a stateless mode, but responses include raw_prompt and raw_generation fields that the quickstart strips by hand. The North API has no standalone search endpoint, and sized search results come from the separate Compass API (15 of 25). List endpoints take limit and offset, and Compass search takes limit and cursor (15 of 20). Errors carry error_type, a stable error_code, is_retryable, request_id and field_errors, mirrored in X-North-Error-Code (20). No idempotency keys. is_retryable tells a client which failures are safe to repeat, and North reads readOnlyHint and destructiveHint from the MCP tools it calls (8 of 20). Only stream is required on chat. Official SDKs for Python, TypeScript and Go, and the Open Responses endpoint works with the OpenAI SDK, but the Python and TypeScript SDKs install from each customer's instance (13 of 15). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation.
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.
Transparency & trust Cohere North +12
Cohere North 69
A closed platform under Cohere's terms of use and customer agreements. The North MCP Python SDK is MIT (15). The data deletion page sets out soft and hard deletion schedules, a retention setting that's off by default and what survives a user deletion, and the data syncing page says what is copied into Compass. The privacy policy (1 May 2026) points to the subprocessor list. The terms of use (re-read 4 November, last updated 7 September 2022) let Cohere use API data to improve and benchmark its services and share it with third parties while the security page promises a training opt-out, and we didn't read the enterprise data commitments (20 of 30). No deprecation policy with notice periods. The docs say v2 agents and conversations replace v1 for new integrations without a removal date (6 of 20). The trust centre lists subprocessors with roles and locations, all in the USA for the nine shown, though we didn't open the full list (15 of 20). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation.
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.
Score by category
| Category | Weight | Cohere North | Microsoft MCP Server for Enterprise | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 53 | Microsoft MCP Server for Enterprise +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 29 | Cohere North +56 |
| Agent ergonomics | 13% | 71 | 55 | Cohere North +16 |
| Security & auth | 14% | 77 | 85 | Microsoft MCP Server for Enterprise +8 |
| Payments & pricing | 10% | 0 | 50 | Microsoft MCP Server for Enterprise +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 68 | 43 | Cohere North +25 |
| Transparency & trust | 7% | 69 | 57 | Cohere North +12 |
| Negative events | ≤15 | -4 | 0 | |
| Total | D 53.2/100 | C 54.1/100 |
Facts side by side
| Fact | Cohere North | Microsoft MCP Server for Enterprise |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Cohere | Microsoft |
| Hosted endpoint | no (local only) | https://mcp.svc.cloud.microsoft/enterprise |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth | OAuth |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Proprietary platform under Cohere's terms of use and customer agreements. The North MCP Python SDK on GitHub is MIT | Closed service under the Microsoft APIs Terms of Use |
| Tools exposed | none | 3 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-01 | 2026-11-17 |
| Terms last updated | 2022-09-07 | 2025-10-01 |
| Privacy policy last updated | 2026-05-01 | 2026-09-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 2.5/5 (2) | none |
How the scores have moved
Microsoft MCP Server for Enterprise
No score change since it was listed.
Verdicts
Cohere North
North has a public OpenAPI 3.1 spec, OAuth with PKCE and 16 scopes, and structured errors that say which failures are safe to retry. Access is the main limitation. Pricing is by sales only, with no trial, no North status history could be read and no SLA was found. The latest dated release found is v1.15.4 of 1 October 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
Cohere North
- Get the North host from your admin and call https://<host>/api. Cohere-hosted examples use north.cohere.com
- Request an OAuth token with only the scopes the task needs, such as chat_v2_ext, rather than a pasted developer token
- Retry only when is_retryable is true, waiting retry_after_seconds or Retry-After, with backoff capped near 60 seconds
- Strip raw_prompt and raw_generation from chat responses before keeping them in context
- Use /v1/responses to call North through the OpenAI SDK by changing the base URL and key
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
Questions
Which is better for AI agents, Cohere North or Microsoft MCP Server for Enterprise?
Microsoft MCP Server for Enterprise and Cohere North score within a point of each other on agent readiness, 54.1 (C) and 53.2 (D). Cohere North leads on schema & documentation, agent ergonomics, maintenance & community and transparency & trust.
Do Cohere North and Microsoft MCP Server for Enterprise need an API key?
Both use an OAuth sign-in.
Can an agent call Cohere North and Microsoft MCP Server for Enterprise without installing anything?
No hosted endpoint is listed for Cohere North. Microsoft MCP Server for Enterprise has a hosted endpoint at https://mcp.svc.cloud.microsoft/enterprise.
Other comparisons with Cohere North or Microsoft MCP Server for Enterprise
- Alation vs Cohere North
- Alation vs Microsoft MCP Server for Enterprise
- Atlan vs Cohere North
- Atlan vs Microsoft MCP Server for Enterprise
- Cohere North vs Collibra
- Cohere North vs Dust
- Cohere North vs Gemini Enterprise
- Cohere North vs Glean
- Cohere North vs Guru
- Cohere North vs Hexis Cloud
- Cohere North vs Onyx
- Cohere North vs Overclock
- Cohere North vs Procore AI Go
- Cohere North vs Secoda
- Cohere North vs Lens (Thought Industries)
- Collibra vs Microsoft MCP Server for Enterprise
- Dust vs Microsoft MCP Server for Enterprise
- Gemini Enterprise vs Microsoft MCP Server for Enterprise
- Glean vs Microsoft MCP Server for Enterprise
- Guru vs Microsoft MCP Server for Enterprise
- Hexis Cloud vs Microsoft MCP Server for Enterprise
- Microsoft MCP Server for Enterprise 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)
Machine-readable
- This page as Markdown
/compare/cohere-north-vs-microsoft-mcp-server-enterprise.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cohere-north.json·/api/v1/tools/microsoft-mcp-server-enterprise.json - From a terminal
anchor compare cohere-north microsoft-mcp-server-enterprise(the CLI) - Over MCP
compare_tools {"a": "cohere-north", "b": "microsoft-mcp-server-enterprise"}at/mcp, no key