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.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldMem0 MCPWatchlist candidateExcel MCP ServerMCP100 Selected
Task fit
Best for
  • Persistent agent memory backed by Mem0 Platform
  • Users who want a hosted MCP endpoint instead of running the archived local server
  • Reading, creating, formatting, charting, and updating XLSX workbooks and worksheets, including formulas and pivot tables
Not ideal for
  • Sensitive memory stores without clear retention/deletion/account controls
  • Workflows where the AI should never persist user data
  • Workbooks that depend on full desktop Excel behavior, macros, or manual visual review
Avoid when
  • You cannot define acceptable memory retention and deletion policy
  • You do not trust the AI client with add/update/delete memory permissions
  • You cannot restrict file access or are using a version affected by CVE-2026-40576
Provenance
Provenance details

First-party MCP

Mem0 · Publisher source ↗

Community implementation

Haris Musa · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Apr 12, 2026

Package: Apr 12, 2026

Popularity evidence
GitHub starsNot documented

4,108

GitHub stars · checked 2026-08-14T18:46:26.000Z

Package downloads / 30 daysNo reliable download data

225,905

package downloads / 30 days · checked 2026-09-08

Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationRequires a Mem0 Platform account/API key for the hosted MCP setup.Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted.
CostMem0 Platform pricing/limits apply.The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply.
PermissionsTools can add, search, retrieve, update, and delete long-term memories within the Mem0 account scope.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 handlingUser/agent memory content is stored in Mem0 Platform and may persist across sessions until updated/deleted according to the account's controls.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
  • Cloud hosting simplifies setup but introduces a third-party data boundary
  • Memory writes can create durable effects that outlive the current session
  • It provides deep spreadsheet manipulation without desktop Excel, but write tools can overwrite data and remote transports add network and filesystem exposure.
Risk contextHigh for sensitive contexts. Persistent memory can store private content and delete/update operations are durable; tenant, retention, audit, and revocation controls need periodic review.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 review2026-09-112026-08-13
Candidate evidence2026-09-11T00:00:00.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →