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

SupermemoryExcel MCP Server

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

Comparable alternatives

Azure MCP ServerMCP100 SelectedChrome DevTools MCPMCP100 SelectedContext7 MCPMCP100 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 SelectedPlaywright MCPMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	SupermemoryWatchlist candidate	Excel MCP ServerMCP100 Selected
Task fit
Best for	Users who want persistent cross-session memory/recall with explicit project scoping.	Reading, creating, formatting, charting, and updating XLSX workbooks and worksheets, including formulas and pivot tables
Not ideal for	Privacy-sensitive workflows that should not persist conversation/project memory outside the client.	Workbooks that depend on full desktop Excel behavior, macros, or manual visual review
Avoid when	Do not store secrets or sensitive personal/project data unless Supermemory retention/project boundaries meet your requirements.	You cannot restrict file access or are using a version affected by CVE-2026-40576
Provenance
Provenance details	First-party MCP endpoint:https: · Publisher source ↗	Community implementation Haris Musa · Publisher source ↗
Maintenance
Maintenance details	Stale Repo: Not documented Package: Not documented	Repo: Apr 12, 2026 Package: Apr 12, 2026
Popularity evidence
GitHub stars	Not documented	4,108 GitHub stars · checked 2026-08-14T18:46:26.000Z
Package downloads / 30 days	No reliable download data	225,905 package downloads / 30 days · checked 2026-09-08
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	OAuth is the default; API key/Bearer authentication is an alternative.	Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted.
Cost	Supermemory plan/API limits and model/provider costs apply.	The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply.
Permissions	Can add/read persistent memories available to the authorized account/project.	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	Submitted memories are intentionally persisted by the Supermemory service; project scoping and retention are therefore central privacy 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	Promising signal, but it ranks below the current Selected/Watchlist admission cohort on maturity, uniqueness, publisher trust, security clarity, or MCP-native evidence.	It provides deep spreadsheet manipulation without desktop Excel, but write tools can overwrite data and remote transports add network and filesystem exposure.
Risk context	Intentional persistent storage can retain sensitive context beyond the current session.	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-09-13T00:00:00Z	2026-08-13
Candidate evidence	2026-09-13T00:00:00Z	2026-08-14T18:46:26.000Z

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

Read the evidence method →