# Mem0 Platform + MCP vs Memori (slim)

> Memori scores 44.2 (E) to Mem0 Platform's 40.1 (E) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/mem0-vs-memori.md (~4,350 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/mem0-vs-memori.json · canonical https://www.anchorterminal.com/compare/mem0-vs-memori
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Memori scores 44.2 (E) on agent readiness against Mem0 Platform + MCP's 40.1 (E), and leads in 3 of 7 scored categories. Mem0 Platform + MCP leads on schema & documentation, maintenance & community and transparency & trust. Both do agent memory.

- Mem0 Platform + MCP: E 40.1, rank #1310 of 1486 · https://www.anchorterminal.com/tools/mem0.min.md
- Memori: E 44.2, rank #1214 of 1486 · https://www.anchorterminal.com/tools/memori.min.md
- Mem0 Platform + MCP, good 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 Schema & documentation, 80 against 68; Maintenance & community, 75 against 33; Transparency & trust, 62 against 52. Also Free to start without a card.
- Memori, good for Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients. Ahead on Payments & pricing, 45 against 40.

| Category | Mem0 Platform + MCP | Memori |
| --- | --- | --- |
| Reliability (16%) | 25 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 68 |
| Agent ergonomics (13%) | 63 | 65 |
| Security & auth (14%) | 45 | 45 |
| Payments & pricing (10%) | 40 | 45 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 33 |
| Transparency & trust (7%) | 62 | 52 |

| Fact (where they differ) | Mem0 Platform + MCP | Memori |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Mem0 | Memori Labs Inc. |
| Hosted endpoint | `https://api.mem0.ai` | `https://api.memorilabs.ai/mcp/` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Tools exposed | 11 | 7 |
| MCP registry | `io.github.mem0ai/mem0` | not listed |
| Last release | 2026-09-25 | 2026-05-27 |
| Terms last updated | no date given | no document linked |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 66k stars, 168k npm/wk, 502k PyPI/wk | 17k stars, 130 npm/wk, 3.8k PyPI/wk |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Maintenance & community, Mem0 Platform + MCP +42: 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.); Memori 33 (SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.)
- Schema & documentation, Mem0 Platform + MCP +12: 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.); Memori 68 (No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid `source` and `signal` pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.)
- Transparency & trust, Mem0 Platform + MCP +10: Mem0 Platform + MCP 62 (The extraction library is Apache-2.0, but the Platform, the product listed here, is closed (20 of 30). Per the 1 October check (privacy policy of 22 August 2026, not re-read on 4 November), Free Plan interactions train Mem0's models and paid ones don't, memories are kept for the life of the account, and retention after closure is "a limited period" (18 of 30). Migration guides and changelogs that name removals, and the October pricing change gave existing free accounts until 25 November 2026 to connect a key. No written deprecation policy (10 of 20). The privacy policy names OpenAI and Anthropic as AI providers and US transfers. No full subprocessor list was found (8 of 20). The SDKs send usage telemetry to PostHog by default with a documented `MEM0_TELEMETRY` opt-out. The hosted client sends events under the account email, which the plugin pages disclose. No term. 20+18+10+8 = 56.); Memori 52 (Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.)
- Payments & pricing, Memori +5: Mem0 Platform + MCP 40 (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.); Memori 45 (No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the `memori_signup` MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.)