Head to head · Agent memory · October 2026 research run
Mem0 Platform + MCP vs Zep
Zep scores 72.9 (BB) on agent readiness against Mem0 Platform + MCP's 42.6 (E), and leads in 5 of 7 scored categories. Mem0 Platform + MCP leads on payments & pricing. Both do agent memory.
Best memory layers for AI agents · All 383 memory comparisons
Which one, for what
Best for Chat products that want per-user facts back with one search call and little setup, and teams willing to connect their own LLM key for higher free limits.
Ahead on
- Payments & pricing, 60 against 45
Also in its favour
- Open source
Watch for
Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026
Zep BB
Best for Agents that must track how facts about a person or account change over time, inside a team that needs access policies and audit logs.
Ahead on
- Reliability, 70 against 25
- Schema & documentation, 93 against 80
- Agent ergonomics, 87 against 63
- Security & auth, 84 against 45
- Maintenance & community, 80 against 75
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 4.0 against 2.5 out of 5
Watch for
The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Zep +45
Mem0 Platform + MCP 25
A status page exists at status.mem0.ai. On 1 October it refused automated readers, so its components weren't seen (10 of 20, a partial value kept and flagged) and it had no readable history (5). Mem0's terms bar automated download from its service and documentation, so the page wasn't requested on 4 November. No Platform rate limits with numbers. The docs say only "Managed quotas per workspace" (0). The OpenAPI file in the repository documents 429 on one operation, a profile-job cooldown with retry_after_seconds, and no general retry guidance was found (0). The October pricing FAQ says an SLA comes only by talking to sales, and the platform comparison page says a support SLA "is not documented as a Platform benefit today" (0, from 5). The v3 API and the hosted MCP server are generally available (10). 10+5+0+0+0+10 = 25.
Zep 70
Atlassian Statuspage at status.getzep.com tracking API, Web App and Episode Processing, with history and feeds (20). The 90 days from 3 August to 1 November hold six incidents. Two impaired core functions for over an hour, retrieval and episode processing on 27 August (about 2.5 hours) and errors and latency during the AWS us-west-2 outage on 3 September (about 2 hours). Two were search latency on 10 and 15 September (2.5 and 3.5 hours). On 16 October an elevated API error rate across all three components was posted at 08:25 PDT, a fix was in place at 08:44 and the incident closed at 11:48. The page doesn't say how long errors lasted after the fix, so it can't be shown to be an hour of wide errors and counts as minor. On 30 October elevated API errors and latency on the API component, marked minor, were posted at 13:36 PDT, recovering by 14:01 and resolved at 17:20, also minor. We count two majors as 5, between the rubric's 10 for one and 0 for several. Limits published per plan, 600 requests a minute on Flex and 1,000 on Flex Plus, with a 5 RPM penalty mode on Free (15). 429 with Retry-After, X-RateLimit headers and backoff-with-jitter guidance, and since v4 an Idempotency-Key for any state-changing call, which the SDKs also send on their own retries of create calls (15). Enterprise names "guaranteed rate limits with SLA" with no published figure (5 of 10). The v4 API is generally available since 14 October (10).
Security & auth Zep +39
Mem0 Platform + MCP 45
Plain revocable API keys in an Authorization: Token header, and browser OAuth on the MCP server with no scopes documented (20 of 30). No read-only key or MCP mode, and delete_all_memories and delete_entities sit in the default MCP tool list. Bulk deletes need at least one filter (3 of 20). The tool returns stored memories that came from user text, and no prompt-injection guidance was found (0). An events API lists memory operations, and audit logs are an Enterprise item (10 of 15). SECURITY.md takes private reports by GitHub advisory or email with a 72-hour acknowledgement, and Mem0 published its first repository advisory (GHSA-5324-3w58-qpp2) on 28 October 2026. SOC 2 Type I claimed per the 1 October check, no security.txt and no bug bounty (12 of 20). 20+3+0+10+12 = 45.
Zep 84
Project API keys can carry ABAC policies that limit which actions and context each agent reaches, and since 14 October graph selectors can limit a key to named standalone graphs. The MCP server uses OAuth 2.1 with PKCE through Google Workspace or, on Enterprise, a custom OIDC provider. We found no key expiry or rotation documentation (27 of 30). MCP connections can be set read-only by an administrator, an account-level switch turns off all MCP writes, and ABAC applies least privilege, but we found no confirmation step for deletes (15 of 20). A memory-security guide treats every context block as untrusted data and covers write control, provenance and keeping instructions out of memory, re-read on 1 November (15). Audit logs for member, key, project and data operations per the 1 October check, with the governance page still listing audit logging on 1 November, and API logs kept 1 day on Flex, 7 on Flex Plus and a year on Enterprise, re-read on the pricing page on 1 November (15). SOC 2 Type II, HIPAA BAA on Enterprise and BYOK, but no security.txt (404 on 1 November), disclosure policy or bug bounty found (12 of 20).
Agent ergonomics Zep +24
Mem0 Platform + MCP 63
The hosted MCP server has 11 tools, unchanged in the docs source (15), with no toolsets or read-only subset to add back. Pagination with page and page_size up to 200 and structured filters on list and search (20). Errors are thin. Few operations document 401, 403 or 429 and there's no error catalogue (8 of 20). No idempotency keys, and no readOnlyHint or destructiveHint documented on the MCP tools. Writes return an event ID that get_event_status can check (5 of 20). Python and TypeScript SDKs and a short required set (user_id plus messages) on add (15). 15+20+8+5+15 = 63.
Zep 87
The Context MCP Server (formerly Memory MCP) has 12 tools, 10 read and 2 write (15), and an administrator can switch a connection to read-only, with an account-level switch that turns off all writes (5 added back). v4 list methods page with an opaque cursor and default to 50 items, each search scope has its own method, and graph.get_subgraph reports truncated and the limit that stopped it (20). Every v4 error carries a stable code, the field at fault in param and a request ID, and the announcement gives the action for codes such as invalid_identifier, not_found and rate_limited. We didn't see the MCP server's error shape or a full code list (18 of 20). The v4 SDKs send an idempotency key when they retry a create call, and callers can pass their own Idempotency-Key. MCP tools are described as read or write, and readOnlyHint or destructiveHint annotations aren't confirmed (14 of 20). SDKs in Python, TypeScript and Go, and an episode add needs only data (15).
Payments & pricing Mem0 Platform + MCP +15
Mem0 Platform + MCP 60
No x402, MPP or L402 (0). Since 26 October 2026 the Starter, Growth and Pro plans are no longer sold to new accounts, per the pricing FAQ. Above the free limits a customer turns on usage-based billing, whose rate "is shown when you turn it on" in the dashboard, or talks to sales, so no per-unit price is published (0, from 10). The free plan needs no card. For the first 30 days Mem0 pays for the model calls (10,000 adds and 1,000 retrievals a month), then adds need the customer's own LLM key, with 50,000 adds and 10,000 retrievals a month (20). mem0 init --agent creates an unclaimed free account with no email, capped at 5 sign-ups a day per IP address (20). 0+0+20+20 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Zep 45
No x402, MPP or L402 (0). Credits are priced per unit and public, 1 credit per 350 bytes of episode, overage $25 per 10,000 on Flex and $75 per 40,000 on Flex Plus (20). Free has 10,000 credits a month, but the pricing page re-read on 1 November still doesn't say whether a card is needed (10 of 20). A person signs up in the browser and creates a project key, and the MCP server needs a human identity-provider sign-in (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Schema & documentation Zep +13
Mem0 Platform + MCP 80
OpenAPI 3.0.1 file in the docs source (docs/openapi.json, last changed 24 September 2026) with 47 paths and 68 operations, which the 1 October note counted as 16 paths (25). llms.txt with a "Use when" line for each page, per the 1 October check (10). The hosted MCP source isn't public, and the 11 documented tool descriptions are one line each with no when-not-to-use (12 of 20). Enums for entity types and event statuses and required fields, but search and list filters are open objects with AND, OR and NOT operators (10 of 15). Examples throughout. 400 is documented on 28 operations and 404 on 26, but 401 on only 5, 429 on 1 and no 5xx catalogue (8 of 15). v1, v2 and v3 paths, migration guides and dated SDK and platform changelogs (15). 25+10+12+10+8+15 = 80.
Zep 93
OpenAPI 3.1 for v4 (147 paths, server api.getzep.com/api/v4) at help.getzep.com/openapi/sdk-reference.json, reached from the index at help.getzep.com/openapi.json that llms.txt names. The v3 link the listing carried returned 404 on 17 October (25). llms.txt per version, a Markdown copy of every page at .md, and a docs MCP server (10). SDK reference pages say what each call does, the MCP tools are labelled read or write, and the Context MCP Server page says to search first and keep the navigation tools for questions about how entities relate (16 of 20). Typed inputs with enums (text, json, message) and stated limits, such as document_id 1 to 100 characters and at most 10 metadata keys, per the 1 October check (13 of 15). Examples in three SDK languages, and the v4 spec lists 400, 401, 403 and 404 responses on almost every operation with one error object (code, message, param, details, request_id). We found no complete list of codes (14 of 15). v2, v3 and v4 docs and a dated changelog with entries through 15 October (15).
Maintenance & community Zep +5
Mem0 Platform + MCP 75
The newest releases are Python mem0ai 2.2.1 and npm mem0ai 3.3.1 of 25 September 2026 (tags v2.2.1 and ts-v3.3.1), 40 days ago, and no package, CLI or plugin tag is newer (20, from 30, cause time). In the 90 days from 6 August, Python v2.0.18 (12 August), v2.0.19 (24 August), v2.0.20 (2 September), v2.1.0 (18 September), v2.2.0 (24 September) and v2.2.1, with the matching TypeScript releases (20). Issues and pull requests weren't re-read (github.com refused). 15 of 25 per the 1 October check. Current Python and TypeScript SDKs, and the hosted MCP server is in the official registry as io.github.mem0ai/mem0 per the 1 October check (15). CI workflows run on pull requests, with run state unread (5 of 10). 20+20+15+15+5 = 75.
Zep 80
SDKs 4.0.1 for Python, TypeScript and Go on 2026-10-20, adding task filters, after 4.0.0 on 14 October, the release that made v4 generally available (30). Seven stable TypeScript SDK releases in the 90 days from 3 August, 3.26.0 to 3.30.0 and 4.0.0 per npm on 17 October and 4.0.1 tagged on 20 October, and dated changelog entries on most days from 9 to 28 October (20). Closed service, scored on the 15-point scale. The changelog is public and frequent, and we didn't test a support channel (10 of 15). Current official SDKs for Python, TypeScript and Go at 4.0.1 (15). The zep-python repository runs mypy and pytest in CI on main, still on Python 3.9, and now carries v4.0.0 and v4.0.1 tags, but we couldn't read CI results or PyPI (5 of 10). Zep's own servers aren't in the official MCP registry.
Score by category
| Category | Weight | Mem0 Platform + MCP | Zep | Edge |
|---|---|---|---|---|
| Reliability | 16% | 25 | 70 | Zep +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 93 | Zep +13 |
| Agent ergonomics | 13% | 63 | 87 | Zep +24 |
| Security & auth | 14% | 45 | 84 | Zep +39 |
| Payments & pricing | 10% | 60 | 45 | Mem0 Platform + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 80 | Zep +5 |
| Transparency & trust | 7% | 62 | 61 | Mem0 Platform + MCP +1 |
| Negative events | ≤15 | -13 | -3 | |
| Total | E 42.6/100 | BB 72.9/100 |
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/v4 |
| 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.mem0ai/mem0 | not listed |
| Last release | 2026-09-25 | 2026-10-20 |
| Terms last updated | no date given | 2026-08-17 |
| Privacy policy last updated | no date given | 2024-01-27 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| 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) |
The panel on both
2 of the 2 reviewers who reviewed both rate Zep higher.
| Reviewer | Mem0 Platform + MCP | Zep |
|---|---|---|
| WardenSecurity auditor | 2/5 Free-plan memories train the vendor's models | 4/5 The best boundaries here, and a perpetual licence to the contents |
| QuillDocumentation and schema critic | 3/5 Eleven tools, and only 400 and 404 documented | 4/5 Twelve tools labelled read or write, and a 429 that says when to retry |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Mem0 Platform + MCP
An agent can create its own free account with mem0 init --agent, no email and no card, and free limits rise to 50,000 adds a month with the customer's own LLM key. Paid plans are no longer sold to new accounts, no usage rate is published, and six advisories on the library appeared between May and October 2026.
Zep
Facts that new data invalidates keep the time they stopped being true, and the v4 API adds stable error codes and safe retries. The terms of 17 August 2026 grant a perpetual, irrevocable licence to train models on customer data.
Before you call either
Mem0 Platform + MCP
- Send the REST key as
Authorization: Token <key>, and the MCP key as Bearer - Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID
- Never pass an empty
user_idor other entity ID to delete_all. The docs say an empty ID matches every memory in the project - After a free account's first 30 days, connect an LLM key in Settings, or adds return an error while searches keep working
- Set
MEM0_TELEMETRY=falseto stop the SDK's PostHog events, which the hosted client sends under the account email
Zep
- Use the 4.0.1 SDKs and store the UUID each create call returns. v4 calls take Zep UUIDs, not your own user or thread IDs
- Set
return_contextwhen adding messages to skip a second round trip - Keep episodes short. Every 350 bytes past the first costs another credit
- Branch on
error.code. On a 429, wait for Retry-After with jitter. Free accounts over quota drop to 5 requests a minute - Send an
Idempotency-Keyon any create call your code may repeat, and expect a delay after an add (202 Accepted) before new facts show up in search
Questions
Which is better for AI agents, Mem0 Platform + MCP or Zep?
Zep scores 72.9 (BB) on agent readiness against Mem0 Platform + MCP's 42.6 (E), and leads in 5 of 7 scored categories. Mem0 Platform + MCP leads on payments & pricing.
Do Mem0 Platform + MCP and Zep need an API key?
Mem0 Platform + MCP needs an API key. Zep takes an API key or an OAuth sign-in.
Can an agent call Mem0 Platform + MCP and Zep without installing anything?
Yes. Mem0 Platform + MCP has a hosted endpoint at https://api.mem0.ai and Zep at https://api.getzep.com/api/v4.
Are Mem0 Platform + MCP and Zep open source?
Mem0 Platform + MCP is open source (Apache-2.0). No open-source release is listed for Zep.
Other comparisons with Mem0 Platform + MCP or Zep
- Amazon Bedrock AgentCore Memory vs Mem0 Platform + MCP
- Amazon Bedrock AgentCore Memory vs Zep
- Basic Memory vs Mem0 Platform + MCP
- Basic Memory vs Zep
- Beacon vs Mem0 Platform + MCP
- Beacon vs Zep
- claude-mem vs Mem0 Platform + MCP
- claude-mem vs Zep
- Cognee vs Mem0 Platform + MCP
- Cognee vs Zep
- EverOS vs Mem0 Platform + MCP
- EverOS vs Zep
- Agent Platform Memory Bank vs Mem0 Platform + MCP
- Agent Platform Memory Bank vs Zep
- Graphiti vs Mem0 Platform + MCP
- Graphiti vs Zep
- Hindsight vs Mem0 Platform + MCP
- Hindsight vs Zep
- Honcho vs Mem0 Platform + MCP
- Honcho vs Zep
- Hy Memory vs Mem0 Platform + MCP
- Hy Memory vs Zep
- LangMem vs Mem0 Platform + MCP
- LangMem vs Zep
- LocalGhost vs Mem0 Platform + MCP
- LocalGhost vs Zep
- Mem0 Platform + MCP vs MemMachine
- Mem0 Platform + MCP vs Memori
- Mem0 Platform + MCP vs Memory (MCP reference server)
- Mem0 Platform + MCP vs MemPalace
- Mem0 Platform + MCP vs past.dev
- Mem0 Platform + MCP vs Supermemory API + MCP
- Mem0 Platform + MCP vs TencentDB Agent Memory
- Mem0 Platform + MCP vs Tokenrip
- MemMachine vs Zep
- Memori vs Zep
- Memory (MCP reference server) vs Zep
- MemPalace vs Zep
- past.dev vs Zep
- Supermemory API + MCP vs Zep
- TencentDB Agent Memory vs Zep
- Tokenrip vs Zep
- AI Memory vs Mem0 Platform + MCP
- AI Memory vs Zep
- Context Mode Engine vs Mem0 Platform + MCP
- Context Mode Engine vs Zep
- Graphicle vs Mem0 Platform + MCP
- Graphicle vs Zep
Machine-readable
- This page as Markdown
/compare/mem0-vs-zep.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mem0.json·/api/v1/tools/zep.json - From a terminal
anchor compare mem0 zep(the CLI) - Over MCP
compare_tools {"a": "mem0", "b": "zep"}at/mcp, no key