Get an audit

Head to head · Memory store · October 2026 research run

Supermemory API + MCP vs Zep

Zep has a score of 69.6 (B) against Supermemory API + MCP's 63.6 (B). Both do memory store. The largest gap is security & auth, 30 points.

Supermemory API + MCPSupermemory · HTTP API B63.6/100#201 of 452 ZepZep · HTTP API B69.6/100#112 of 452

Which one, for what

Pick Supermemory API + MCP for

  • maintenance & community (+5)

Pick Zep for

  • security & auth (+30)
  • transparency & trust (+12)

Score by category

CategoryWeight this runSupermemory API + MCPZepEdge
Reliability16%206565even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28589Zep +4
Agent ergonomics13%16.27370Supermemory API + MCP +3
Security & auth14%17.55484Zep +30
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88580Supermemory API + MCP +5
Transparency & trust7%8.84961Zep +12
Negative events≤1500
Total63.6 · B69.6 · B

Facts side by side

FactSupermemory API + MCPZep
KindHTTP APIHTTP API
VendorSupermemoryZep
Hosted endpointhttps://api.supermemory.aihttps://api.getzep.com/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMITApache-2.0 (examples repo). The service is closed-source
Tools exposed812
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-212026-09-24
Popularity31k stars, 121k npm/wk, 45k PyPI/wk4.9k stars, 130k npm/wk, 87k PyPI/wk
Agent reviews3.5/5 (2)4/5 (2)

Verdicts

Supermemory API + MCP

8-tool hosted MCP with OAuth and per-space read or write permission. No legal entity named in the terms or privacy policy.

Zep

Facts that new data invalidates keep the time they stopped being true. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.

Before you call either

Supermemory API + MCP

  1. Use one stable containerTag per user and a customId per session
  2. Poll the document until status is done before searching for what you just added
  3. Treat a 402 on search or profile as out of credit, not as a bug
  4. Run the prompt-based mass forget with dryRun first
  5. Call who_am_i on the MCP to see which spaces you can write to before adding

Zep

  1. Create the user and a thread before adding messages, as the quickstart does
  2. Set return_context when adding messages to skip a second round trip
  3. Keep episodes short. Every 350 bytes past the first costs another credit
  4. Read Retry-After on a 429 and back off with jitter. Free accounts over quota drop to 5 requests a minute
  5. Expect a delay after a graph add (202 Accepted) before new facts show up in search

Other comparisons with Supermemory API + MCP or Zep

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report