Head to head · Agent memory · October 2026 research run
claude-mem vs MemPalace
MemPalace scores 65.7 (B) on agent readiness against claude-mem's 58.6 (C), and leads in 5 of 7 scored categories. claude-mem leads on reliability. Both do agent memory.
Best memory layers for AI agents · All 188 memory comparisons
Which one, for what
Best for Session memory for one developer's coding agents, recalled by staged MCP search, with optional hosted sync across machines.
Ahead on
- Reliability, 85 against 77
Watch for
Telemetry is on by default and secret redaction is off by default
Best for Verbatim, local, searchable memory of coding-agent sessions
Ahead on
- Payments & pricing, 60 against 20
- Transparency & trust, 58 against 46
Also in its favour
- No key needed to call it
- Free to start without a card
Watch for
Search returns stored conversations and mined files verbatim, and no prompt-injection guidance was found in the docs or skills
Score by category
| Category | Weight this run | claude-mem | MemPalace | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 85 | 77 | claude-mem +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 85 | MemPalace +1 |
| Agent ergonomics | 13%16.2 | 74 | 75 | MemPalace +1 |
| Security & auth | 14%17.5 | 50 | 53 | MemPalace +3 |
| Payments & pricing | 10%12.5 | 20 | 60 | MemPalace +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 74 | claude-mem +2 |
| Transparency & trust | 7%8.8 | 46 | 58 | MemPalace +12 |
| Negative events | ≤15 | -6 | -4 | |
| Total | C 58.6/100 | B 65.7/100 |
Facts side by side
| Fact | claude-mem | MemPalace |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | Alex Newman | MemPalace (open-source project) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio, HTTP | stdio, Streamable HTTP |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms | MIT |
| Tools exposed | 19 | 47 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-29 | 2026-10-14 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 106k stars, 30k npm/wk | 60k stars |
Verdicts
claude-mem
Typed MCP tools with a staged search, loopback-only local services and very frequent releases with passing CI on main. Telemetry and secret redaction defaults, a privacy page that understates what leaves the machine, and a host permission bypass fixed on 26 October 2026 mean an operator should review settings before use.
MemPalace
Local by default and MIT, with typed input schemas on all 47 MCP tools, a three-tool light server, a read-only mode, passing CI and roughly monthly releases. Recall returns stored conversation text verbatim with no prompt-injection guidance, the HTTP hub has one all-powerful token, and launch benchmark claims were retracted in April 2026.
Before you call either
claude-mem
- Install with
npx claude-mem install --provider claude(or another provider) to skip the cmem.ai sign-in;npm install -g claude-meminstalls only the library, not the hooks or worker. - Set
CLAUDE_MEM_REDACT_ENABLED=truebefore capturing sessions that print keys or tokens, and wrap sensitive prompt text in<private>tags. - Run
npx claude-mem telemetry disableor setDO_NOT_TRACK=1if analytics shouldn't leave the machine. - Search in order,
searchthentimelinethenget_observationswith selected IDs; useget_tool_usesonly when a summary isn't enough, since it returns raw tool I/O. - Treat recalled observations as data, since they summarise earlier tool output, which can include text from web pages or files.
MemPalace
- Install only from PyPI
mempalace, ghcr.io/mempalace/mempalace or the GitHub repository; the project warns that other MemPalace domains such as mempalace.tech have distributed malware. - Treat drawers returned by
mempalace_searchandmempalace_get_draweras untrusted text, since they hold verbatim transcripts and mined files, never as instructions. - Use
mempalace-light-mcp(3 tools) ormempalace serve --read-onlywhen the agent only needs recall; the default server lists 47 tools. - Call
mempalace_delete_by_sourcefirst with its default dry run and check the count; deletes are irreversible and remove revisions. - On a non-loopback
mempalace serve, sendAuthorization: Bearer <token>from~/.mempalace/server/<key>/tokenand put TLS in front; never run--allow-insecureon an open network.
Questions
Which is better for AI agents, claude-mem or MemPalace?
MemPalace scores 65.7 (B) on agent readiness against claude-mem's 58.6 (C), and leads in 5 of 7 scored categories. claude-mem leads on reliability.
Do claude-mem and MemPalace need an API key?
claude-mem takes an API key or an OAuth sign-in. MemPalace needs no key.
Can an agent call claude-mem and MemPalace without installing anything?
claude-mem runs on your own machine, with no hosted endpoint listed. MemPalace runs on your own machine, with no hosted endpoint listed.
Are claude-mem and MemPalace open source?
Yes. claude-mem is open source (Apache-2.0 for the engine, CLI, worker, MCP tools, adapters and docs. The hosted CMEM Pro observer, cloud sync and TeamBrain are closed and run under the cmem cloud terms). MemPalace is open source (MIT).
Other comparisons with claude-mem or MemPalace
- Amazon Bedrock AgentCore Memory vs claude-mem
- Amazon Bedrock AgentCore Memory vs MemPalace
- claude-mem vs Cognee
- claude-mem vs Graphicle
- claude-mem vs Graphiti
- claude-mem vs Hindsight
- claude-mem vs Honcho
- claude-mem vs Hy Memory
- claude-mem vs LangMem
- claude-mem vs LocalGhost
- claude-mem vs Mem0 Platform + MCP
- claude-mem vs Memory (MCP reference server)
- claude-mem vs past.dev
- claude-mem vs Supermemory API + MCP
- claude-mem vs TencentDB Agent Memory
- claude-mem vs Tokenrip
- claude-mem vs Zep
- Cognee vs MemPalace
- Graphiti vs MemPalace
- Hindsight vs MemPalace
- Honcho vs MemPalace
- Hy Memory vs MemPalace
- LangMem vs MemPalace
- LocalGhost vs MemPalace
- Mem0 Platform + MCP vs MemPalace
- Memory (MCP reference server) vs MemPalace
- MemPalace vs past.dev
- MemPalace vs Supermemory API + MCP
- MemPalace vs TencentDB Agent Memory
- MemPalace vs Tokenrip
- MemPalace vs Zep
- AI Memory vs claude-mem
- AI Memory vs MemPalace
- claude-mem vs Context Mode Engine
- Context Mode Engine vs MemPalace
- Graphicle vs MemPalace
Machine-readable
- This page as Markdown
/compare/claude-mem-vs-mempalace.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/claude-mem.json·/api/v1/tools/mempalace.json - From a terminal
anchor compare claude-mem mempalace(the CLI) - Over MCP
compare_tools {"a": "claude-mem", "b": "mempalace"}at/mcp, no key