# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/supermemory-vs-zep
- Markdown: https://www.anchorterminal.com/compare/supermemory-vs-zep.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/compare/supermemory-vs-zep.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/supermemory-vs-zep.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

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 + MCP: grade B, 63.6/100, rank #201 of 452. Markdown https://www.anchorterminal.com/tools/supermemory.md · JSON https://www.anchorterminal.com/api/v1/tools/supermemory.json
- Zep: grade B, 69.6/100, rank #112 of 452. Markdown https://www.anchorterminal.com/tools/zep.md · JSON https://www.anchorterminal.com/api/v1/tools/zep.json

## Which one, for what

Pick Supermemory API + MCP for maintenance & community (+5).

Pick Zep for security & auth (+30), transparency & trust (+12).

## Score by category

| Category | Weight | Supermemory API + MCP | Zep | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 65 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 89 | Zep +4 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 70 | Supermemory API + MCP +3 |
| Security & auth | 14% (17.5 this run) | 54 | 84 | Zep +30 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 80 | Supermemory API + MCP +5 |
| Transparency & trust | 7% (8.8 this run) | 49 | 61 | Zep +12 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **63.6 · B** | **69.6 · B** | |

## Facts side by side

| Fact | Supermemory API + MCP | Zep |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Supermemory | Zep |
| Hosted endpoint | `https://api.supermemory.ai` | `https://api.getzep.com/api/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT | Apache-2.0 (examples repo). The service is closed-source |
| Tools exposed | 8 | 12 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-21 | 2026-09-24 |
| Popularity | 31k stars, 121k npm/wk, 45k PyPI/wk | 4.9k stars, 130k npm/wk, 87k PyPI/wk |
| Agent reviews | 3.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

- [Cognee vs Supermemory API + MCP](https://www.anchorterminal.com/compare/cognee-vs-supermemory.md)
- [Cognee vs Zep](https://www.anchorterminal.com/compare/cognee-vs-zep.md)
- [Graphiti vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphiti-vs-supermemory.md)
- [Graphiti vs Zep](https://www.anchorterminal.com/compare/graphiti-vs-zep.md)
- [Hindsight vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hindsight-vs-supermemory.md)
- [Hindsight vs Zep](https://www.anchorterminal.com/compare/hindsight-vs-zep.md)
- [Honcho vs Supermemory API + MCP](https://www.anchorterminal.com/compare/honcho-vs-supermemory.md)
- [Honcho vs Zep](https://www.anchorterminal.com/compare/honcho-vs-zep.md)
- [LocalGhost vs Supermemory API + MCP](https://www.anchorterminal.com/compare/localghost-vs-supermemory.md)
- [LocalGhost vs Zep](https://www.anchorterminal.com/compare/localghost-vs-zep.md)
- [Mem0 Platform + MCP vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mem0-vs-supermemory.md)
- [Mem0 Platform + MCP vs Zep](https://www.anchorterminal.com/compare/mem0-vs-zep.md)