Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Microsoft 365 MCP ServerWatchlist candidate | MCP Unity Editor (Game Engine)MCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation Softeria · Publisher source ↗ | Community implementation github:codergamester · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 24, 2026 Package: Aug 24, 2026 | Repo: Aug 10, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 958 GitHub stars · checked 2026-09-08 | 1,865 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| Package downloads / 30 days | 173,619 package downloads / 30 days · checked 2026-09-08 | No reliable download data |
| External adoption evidence |
| Not documented |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | The documented options include Device Code Flow for local stdio, OAuth Authorization Code Flow for HTTP, a caller-supplied MS365_MCP_OAUTH_TOKEN, and a custom Microsoft Entra application for organization or production deployment. Use a dedicated identity, restrict consented Graph scopes, remove the MCP entry and local credentials when access is no longer needed, and revoke Microsoft authorization or tokens through the applicable account or Entra controls. | The WebSocket server defaults to localhost:8090. Remote instructions can bind it to 0.0.0.0; no bearer-token or OAuth mechanism is documented. |
| Cost | The MIT-licensed npm package has no separate package purchase price documented. Access still depends on the Microsoft account, service access, licenses, tenant permissions, and admin consent required by the chosen workload; self-hosted HTTP deployments can also incur normal hosting, container, and secret-management costs. | The publisher describes the MIT-licensed project as free and open source. Unity, Node.js, hosting, client, and model costs are separate. |
| Permissions | The MCP can read and write Microsoft Graph resources including email, calendar, OneDrive files, SharePoint Sites and Lists, Teams/chats/meetings, contacts, users, OneNote, Planner, To Do, and Excel. Organization-mode SharePoint can request broad Sites.Read.All, Sites.ReadWrite.All, and Sites.Manage.All scopes; use --allowed-scopes, --enabled-tools, --read-only, and Sites.Selected where the documented operation supports them. | Executes Unity menus and controls scenes, GameObjects, components, materials, assets, packages, tests, logs, play mode, and project-state resources through a WebSocket bridge. |
| Data handling | The local MCP handles Microsoft Graph request and response data. Documented local MSAL token caching is encrypted, while the headless fallback still depends on directory access controls. The HTTP deployment documents stateless per-request bearer-token Graph requests. Structured audit logging is enabled for Graph-reaching tool calls and can include principals, tool names, outcomes, resource identifiers, and recipient counts or domains; response bodies are not recorded by that structured log, and separate operational logging can record tool parameters. Token and PII redaction is documented as configurable rather than an absolute data-boundary guarantee. | Unity scenes, assets, project state, and console logs are read or modified locally and returned through MCP. Remote transmission, retention, and telemetry are not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | This broad Microsoft Graph MCP can expose sensitive business email, files, SharePoint content, Teams/chats/meetings, contacts, and tenant information, and it includes material write and delete operations. Destructive-operation confirmation is documented as off by default; default organization-mode SharePoint permissions can be broad, and HTTP Dynamic Client Registration is enabled by default unless disabled. Use read-only mode, presets/tool filtering, allowed scopes, Sites.Selected when applicable, dedicated identities, and explicit review before enabling writes or tenant-wide discovery. GHSA-9w34-3f56-vwmh affected versions through 0.136.0; reviewed version 0.146.1 is above the documented 0.137.0 fixed version. This patched advisory is not a general security certification. | Can make destructive project changes, install packages, execute menu items, and control play mode. Keep the bridge loopback-only and supervise all writes and deletions in a version-controlled project. |
| Evidence date | ||
| Editorial review | 2026-08-24T12:00:00.000Z | 2026-08-11 |
| Candidate evidence | 2026-08-24T12:00:00.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →