# Mem0 Platform + MCP vs Zep

> Zep has a score of 69.6 (B) against Mem0 Platform + MCP's 56.6 (C). Both do memory store. The largest gap is security & auth, 39 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/mem0-vs-zep
- Markdown: https://www.anchorterminal.com/compare/mem0-vs-zep.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/compare/mem0-vs-zep.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/mem0-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-05

Zep has a score of 69.6 (B) against Mem0 Platform + MCP's 56.6 (C). Both do memory store. The largest gap is security & auth, 39 points.

- Mem0 Platform + MCP: grade C, 56.6/100, rank #301 of 452. Markdown https://www.anchorterminal.com/tools/mem0.md · JSON https://www.anchorterminal.com/api/v1/tools/mem0.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 Mem0 Platform + MCP for payments & pricing (+20), maintenance & community (+5), transparency & trust (+5).

Pick Zep for reliability (+35), schema & documentation (+9), agent ergonomics (+7), security & auth (+39).

## Score by category

| Category | Weight | Mem0 Platform + MCP | Zep | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 30 | 65 | Zep +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 89 | Zep +9 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 70 | Zep +7 |
| Security & auth | 14% (17.5 this run) | 45 | 84 | Zep +39 |
| Payments & pricing | 10% (12.5 this run) | 50 | 30 | Mem0 Platform + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 80 | Mem0 Platform + MCP +5 |
| Transparency & trust | 7% (8.8 this run) | 66 | 61 | Mem0 Platform + MCP +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **56.6 · C** | **69.6 · B** | |

## Facts side by side

| Fact | Mem0 Platform + MCP | Zep |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Mem0 | Zep |
| Hosted endpoint | `https://api.mem0.ai` | `https://api.getzep.com/api/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 (examples repo). The service is closed-source |
| Tools exposed | 11 | 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 | `io.github.mem0ai/mem0` | not listed |
| Last release | 2026-09-25 | 2026-09-24 |
| Popularity | 66k stars, 168k npm/wk, 502k PyPI/wk | 4.9k stars, 130k npm/wk, 87k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 4/5 (2) |

## Verdicts

**Mem0 Platform + MCP.** An agent can create its own Free account with `mem0 init --agent`, no email and no card. Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026.

**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

### Mem0 Platform + MCP

1. Send the REST key as `Authorization: Token <key>`, and the MCP key as Bearer
2. Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID
3. Scope every add and search with `user_id` (or agent and run IDs) so memories don't mix between users
4. Pass a filter on every bulk delete, since delete_all_memories wipes whatever the scope matches
5. On Hobby and Starter, count retrievals rather than adds. The retrieval quota is a tenth the size

### 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 Mem0 Platform + MCP or Zep

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