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 | Excel MCP ServerMCP100 Selected | codaMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation Haris Musa · Publisher source ↗ | First-party MCP ecosystem:coda · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Apr 12, 2026 Package: Apr 12, 2026 | Repo: Not documented Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 4,108 GitHub stars · checked 2026-08-14T18:46:26.000Z | Not documented |
| External adoption evidence |
| Not documented |
| 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✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted. | The official hosted endpoint supports OAuth 2 and personal access tokens. |
| Cost | The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | 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. | Coda document sharing, user permissions, admin controls, and OAuth or PAT scope determine access. |
| Data handling | 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. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive files & knowledge information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | 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. | Documents and tables can contain broad internal knowledge, and write tools can alter shared operational records. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-08-13 | 2026-07-30 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-07-30T19:00:00.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →