Microsoft 365: MCP server, CLI and agent surfaces
Sign-in required, tools not seen, not counted. The MCP endpoint listed for Microsoft 365 at mcp.svc.cloud.microsoft answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
Fact sheet
| Company | Microsoft 365 (registry title: Microsoft 365 (Enterprise MCP)) |
|---|---|
| Domain | cloud.microsoft |
| Category | Uncategorised (assigned by this directory from the registry description) |
| MCP server | Sign-in required (OAuth without client registration) |
| Tranco rank | 42 on the list of 4 November 2026 |
| Ora score | none: Ora returned no cached score for cloud.microsoft when asked on 5 November 2026 |
| Company found through | the GitHub MCP Registry |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://mcp.svc.cloud.microsoft/enterprise |
|---|---|
| How it was found | listed in the GitHub MCP Registry |
| Transport | streamable-http |
| HTTP status | 401 |
| Connected | 4 November 2026, 20:01 UTC |
| Handshake time | 1,390 ms over 1 attempt |
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:55:52Z https://mcp.svc.cloud.microsoft/enterprise sent initialize result auth-required (HTTP 401) 1180 ms
- 20:01:27Z https://mcp.svc.cloud.microsoft/enterprise sent initialize result auth-required (HTTP 401) 1390 ms
Authentication
| Auth type | OAuth without client registration |
|---|---|
| What the challenge said | Bearer realm="", authorization_uri="https://login.microsoftonline.com/common/oauth2/authorize", client_id="e8c77dc2-69b3-43f4-bc51-3213c9d915b4", resource_metadata="https://mcp.svc.cloud.microsoft/.well-known/oauth-protected-resource/enterprise" |
| Protected resource metadata | mcp.svc.cloud.microsoft |
| Authorization server metadata | login.microsoftonline.com |
The sign-in route, step by step
- Request
https://mcp.svc.cloud.microsoft/enterprisewithout a token. It answers 401 and aWWW-Authenticateheader. - Read the OAuth metadata at
https://login.microsoftonline.com/organizations/v2.0/.well-known/openid-configuration. It lists no registration endpoint. - Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one.
- Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for Microsoft 365. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | No OpenAPI file at the root paths checked. |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | The path answered with a web page, not the file. Not counted. |
| A2A agent card | The path answered with a web page, not the file. Not counted. |
| A2A agent card (older path) | The path answered with a web page, not the file. Not counted. |
| agents.json | The path answered with a web page, not the file. Not counted. |
| OAuth authorization server metadata | The path answered with a web page, not the file. Not counted. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | No |
| GitHub MCP Registry | Yes |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |