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 fieldGraphiti MCPWatchlist candidateExcel MCP ServerMCP100 Selected
Task fit
Best for
  • Self-hosted persistent memory and knowledge-graph workflows
  • Teams willing to isolate the service behind network/auth controls
  • Reading, creating, formatting, charting, and updating XLSX workbooks and worksheets, including formulas and pivot tables
Not ideal for
  • Internet-exposed deployments without a reverse proxy or other access control
  • Production memory stores that require built-in strong authentication
  • Workbooks that depend on full desktop Excel behavior, macros, or manual visual review
Avoid when
  • You would expose the default 0.0.0.0 HTTP endpoint on an untrusted network
  • You cannot back up or recover graph data before enabling delete/clear tools
  • You cannot restrict file access or are using a version affected by CVE-2026-40576
Provenance
Provenance details

First-party MCP

Zep / getzep · 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 CodeLocal stdio
Claude DesktopLocal stdio
CodexLocal stdio
VS CodeLocal stdio
CursorLocal stdio
OpenCodeLocal stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationCurrent MCP server docs do not establish built-in HTTP authentication as a default control; deployments should rely on local access or external network/reverse-proxy controls.Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted.
CostOpen-source server; database and LLM/embedder provider costs apply.The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply.
PermissionsTools include add/search plus delete_episode, delete_entity_edge, and clear_graph. Database privileges are those of the configured Neo4j/FalkorDB credentials.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 handlingStores knowledge-graph episodes/entities/facts and uses configured LLM/embedder providers during ingestion/search. Anonymous telemetry can be disabled.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
  • Rich memory tools are valuable but include destructive operations
  • Multiple LLM/database credentials increase the deployment's secret surface
  • It provides deep spreadsheet manipulation without desktop Excel, but write tools can overwrite data and remote transports add network and filesystem exposure.
Risk contextHigh. Default network exposure plus destructive graph tools and backend/LLM credentials create material unauthorized-access and data-loss risk.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 →