claude-mem vs Memori

claude-mem 75

Scored as local software. Official npm package claude-mem installed through npx claude-mem install, with Node ^20.19.0 or 22.12 and later and Bun 1.1.31 or later stated in package.json (20). ci.yml runs on pushes to main and runs the test lanes (fast and integration), the OpenClaw, My Work, Cowork and Hermes suites, beside Windows, media-runtime and ods-native workflows. The 29 October push runs passed per the 30 October reading of GitHub's API, which answers 403 in this session, so today's result is unread (15 of 25). The 30 October reading counted 129 open issues and pull requests combined, and the changelog records a July 2026 worker restart loop fixed in 13.12.1; reply times weren't re-read (10 of 25). Majors carry breaking changes with migration notes, such as 15.0.0 removing mem_search and flash_search, and 15.7.0 to 15.9.0 list none (15). Version 15.9.0 (15).

Memori 28

Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call memori_quota on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.

claude-mem 76

v15.9.0 tagged on 2 November 2026, with its changelog entry dated the same day (30). Tags v15.0.0 (20 October) to v15.9.0 in the shallow clone alone, 16 in two weeks, and 78 GitHub releases from 1 August to 29 October per the 30 October reading (20). Issue #5078, reported on 26 October 2026, was fixed by a contributor's pull request and released in 15.3.0 the same day; the 15.9.0 notes thank 25 outside contributors; reply times weren't re-read (18 of 25). Not in the official MCP registry per the 30 October search (0). CI configured on main, Dependabot per SECURITY.md, two runtime dependencies in the published package (8 of 10).

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.

claude-mem 20

No x402, MPP or L402 (0). Scored on the hosted option, as the brief says for open-source software with a paid service. CMEM Pro $30, Heavy $70 and CMEM Max $100 a month are public, but the included usage is shown only at checkout (10 of 20). The engine is free with no card, but the pricing page says the CMEM Pro trial needs a credit or debit card while the README says sign-in needs none (10 of 20). The hosted service needs a browser sign-in by magic link (0).

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.

claude-mem 84

Every one of the 26 MCP tools declares a JSON Schema input (25). llms.txt at docs.claude-mem.ai with Markdown copies of each page (10). Descriptions give purpose and order of use (search, then timeline, then get_observations) and say when not to call a tool (get_tool_uses "rarely needed", dumb_search "fast, but shallow"), but the README says recall uses 4 tools and lists 3 while the server advertises 19 (15 of 20). Required fields are marked and some limits have minimum and maximum, but type, orderBy and obs_type are free strings described in prose, limit is a number rather than an integer on most tools, and metadata and fields are open objects (8 of 15). README examples and a worker API reference with 400 and 404 error bodies (11 of 15). Keep a Changelog file and release notes for each version (15).

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.

claude-mem 74

19 tools advertised by default with about 10,000 characters of descriptions across all 26 by our count (15), plus 3 back because TeamBrain and server-only tools stay hidden until used and the work-state tools can be switched off (18 of 25). search takes limit, offset, project, platform source, type, observation type, date range and order, and timeline and get_observations take depth and limit (20). Worker errors are JSON with 400 and 404 documented, and MCP errors name the fix ("Join a team with npx claude-mem teambrain join"), but no error catalogue (14 of 20). 17 tools carry readOnlyHint, none carries destructiveHint or idempotentHint, and work_state_write appends on each call (12 of 20). Most parameters are optional with stated defaults; the only official library is the TypeScript npm package (10 of 15).

Memori 65

Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (15). Total 65.

claude-mem 46

Apache-2.0 engine with the hosted observer, sync and team functions reserved as closed, per docs/ip-boundary.md (25 of 30). SECURITY.md lists every route by which data leaves the machine, but the cmem.ai privacy page, re-read on 4 November, still says "Nothing leaves your device unless you explicitly turn on cloud sync" and that sensitive details are filtered before storage, while secret redaction defaults to off, doesn't cover the hosted observer, and names no retention periods, subprocessors or legal entity. Locally, raw tool uses are kept forever by default (CLAUDE_MEM_TOOL_USES_RETENTION_DAYS 0) and daily logs 30 days since 15.7.0 (12 of 30). Release notes date breaking changes with migration steps, such as 15.0.0 and the removal of Gemini CLI support in 13.10.0, but no written deprecation policy (8 of 20). Telemetry is on by default, documented field by field (including PostHog's city-level location from the sender's IP) with telemetry disable, DO_NOT_TRACK and a separate error-reporting switch, and the installer asks once; the README doesn't mention it (16 of 20).

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.