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 | Office Editor MCPWatchlist candidate | Excel MCP ServerMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation theWDY · Publisher source ↗ | Community implementation Haris Musa · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 13, 2026 Package: Not documented | Repo: Apr 12, 2026 Package: Apr 12, 2026 |
| Popularity evidence | ||
| GitHub stars | 91 GitHub stars · checked 2026-08-14T18:46:26.000Z | 4,108 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio | 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 local stdio servers have no separate authentication. Optional translation and database integrations accept their own API keys or connection strings, which must stay in local configuration. | Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted. |
| Cost | The MIT-licensed source has no documented MCP usage fee. Microsoft Office-dependent features, translation APIs, databases, OCR, and client services may have separate costs. | The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply. |
| Permissions | The servers can read, create, format, overwrite, copy, and in some modes move or delete local documents. OFFICE_EDIT_PATH scopes general operations and OFFICE_ALLOW_DESTRUCTIVE gates move/delete behavior. | The server can read, create, modify, format, chart, and delete workbook content. Remote modes confine relative paths to EXCEL_FILES_PATH in the patched release. |
| Data handling | Office files are processed locally by default. Optional translation, OCR, database import/export, and other integrations can send or retrieve content through configured external services. | Workbook paths and spreadsheet content are processed by the server and returned to the connected client as required by tool calls; publisher telemetry and retention are not documented. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Clone a reviewed revision, install in an isolated environment, set OFFICE_EDIT_PATH to a disposable directory, keep destructive operations disabled, and configure only the single Office server needed for the task. | Versions through 0.1.7 have a critical path-traversal vulnerability. Use 0.1.8 or later, prefer stdio, restrict workbook paths, avoid public remote listeners, and keep recoverable backups. |
| Evidence date | ||
| Editorial review | 2026-08-14 | 2026-08-13 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →