Head to head · Agent memory · October 2026 research run
claude-mem vs Agent Platform Memory Bank
Agent Platform Memory Bank scores 65.6 (B) on agent readiness against claude-mem's 54.6 (C), and leads in 3 of 7 scored categories. claude-mem leads on reliability, schema & documentation and maintenance & community. Both do agent memory.
Best memory layers for AI agents · All 353 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, 75 against 68
- Schema & documentation, 84 against 75
- Maintenance & community, 76 against 62
Also in its favour
- Runs on your own machine
- Open source
Watch for
Setup uploaded the last 30 days of prompts to cmem.ai without asking from 15.2.0 until 15.8.3 (25 October to 2 November 2026)
Best for Managed long-term memory for agents already on Google Cloud, especially with ADK and Agent Platform Sessions.
Ahead on
- Security & auth, 72 against 50
- Transparency & trust, 81 against 46
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where claude-mem loses 8 points for them
Watch for
Needs a Google Cloud project with billing, set up by a person in the console
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.
Transparency & trust Agent Platform Memory Bank +35
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).
Agent Platform Memory Bank 81
Closed service under the Google Cloud terms (15). Data residency at rest, CMEK and the Cloud Data Processing Addendum apply; no Memory Bank retention period or time-to-live was read (20 of 30). The rename was announced in the release notes with old and new names listed, and Google's deprecation policy covers GA services (14 of 20). Google Cloud's subprocessor list and regional endpoints are published (16 of 20). Total 65.
Security & auth Agent Platform Memory Bank +22
claude-mem 50
The worker and MCP HTTP transport bind to loopback and check Host and Origin, with no credential (20), the server beta's cmem_ keys are scoped and stored hashed (5), and the hosted private MCP link is a bearer secret in the URL per the privacy page (less 10), 15 of 30. Plan mode prompts before the writing tools, <private> tags keep content out of storage and work state can be disabled, but hooks capture all tool input and output by default and the Antigravity adapter answered allow to every agy tool call until 26 October 2026 (10 of 20). Stored observations summarise tool output that can carry injected text and are injected at the next SessionStart; we found no guidance on that, and redaction of secrets is off by default (3 of 15). Local logs, the My Work viewer, an SSE event stream and raw tool I/O through get_tool_uses (12 of 15). SECURITY.md (moved to .github/SECURITY.md in 15.8.1) with a private advisory route, a 48-hour acknowledgement and a published fix history; no security.txt, bug bounty or certification (10 of 20).
Agent Platform Memory Bank 72
OAuth 2.0 with IAM and service accounts (30), less 10, as for the other Google API listings, because the v1 discovery document lists access_token, oauth_token and key as query parameters (20 of 30). IAM Conditions can restrict access by memory scope; purge and delete have no confirmation (15 of 20). Memories are written by an LLM from conversation content and returned to agents, with no injection guidance found (5 of 15). Access Transparency and Access Approval are listed; Cloud Audit Logs coverage for Memory Bank wasn't read (12 of 15). Google's valid security.txt, vulnerability reward programme and certifications, with HIPAA listed for Memory Bank (20). Total 72.
Maintenance & community claude-mem +14
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).
Agent Platform Memory Bank 62
The newest Memory Bank release notes are of 20 August 2026 (IngestEvents GA, metadata, Gemini Embedding 2), 78 days before the check, and billing started on 1 September (20). Three Memory Bank entries in the 90 days, all on 20 August (10 of 20). Public release notes and Cloud Customer Care (12 of 15). google-cloud-agentplatform 2.7.0 on 28 October 2026, twelve releases in 90 days per its PyPI release feed, plus ADK (15). SDK test status not checked (5 of 10). Total 62.
Schema & documentation claude-mem +9
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).
Agent Platform Memory Bank 75
Google's discovery document is a machine-readable contract for every memory method (25). No llms.txt or Markdown docs found (0). Method descriptions are 13 to 39 characters, one-line summaries, while the guides explain when to generate from sessions or from direct facts (12 of 20). Typed schemas with required fields in the discovery document (12 of 15). Python examples, a troubleshooting page and a documented 404 for deleted memories (11 of 15). v1 and v1beta1 and dated release notes (15). Total 75.
Reliability claude-mem +7
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).
Agent Platform Memory Bank 68
Hosted lines. Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November 2026, holds four incidents since 8 August (20 August, 27 products; 1 September, us-central1-b; 8 October, Cloud Storage; 20 October, europe-west2, 38 products), and none names Agent Platform, Vertex or Memory Bank (30). No Memory Bank quotas or rate limits were found; the platform quotas path guessed returned 404 (0, unchecked). Generation is a long-running operation with wait and cancel methods, and Google's retry guidance wasn't re-read for this API (8 of 15). No SLA for Memory Bank was found in the pages read (0, unchecked). Memory profiles, IngestEvents and multi-regional endpoints are GA (10). Total 68.
Score by category
| Category | Weight this run | claude-mem | Agent Platform Memory Bank | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 75 | 68 | claude-mem +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 75 | claude-mem +9 |
| Agent ergonomics | 13%16.2 | 74 | 75 | Agent Platform Memory Bank +1 |
| Security & auth | 14%17.5 | 50 | 72 | Agent Platform Memory Bank +22 |
| Payments & pricing | 10%12.5 | 20 | 20 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 76 | 62 | claude-mem +14 |
| Transparency & trust | 7%8.8 | 46 | 81 | Agent Platform Memory Bank +35 |
| Negative events | ≤15 | -8 | 0 | |
| Total | C 54.6/100 | B 65.6/100 |
Facts side by side
| Fact | claude-mem | Agent Platform Memory Bank |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Alex Newman | Google Cloud |
| Hosted endpoint | no (local only) | https://aiplatform.googleapis.com/v1 |
| Transports | stdio, HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| 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 | none |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-02 | 2026-08-20 |
| Terms last updated | couldn't be read | 2026-09-02 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 106k stars, 30k npm/wk | none |
How the scores have moved
Agent Platform Memory Bank
No score change since it was listed.
Verdicts
claude-mem
Typed MCP tools with a staged search, loopback-only local services and releases most days, with tests in CI. The 15.8.3 notes say setup uploaded 30 days of prompt text to cmem.ai without asking from 25 October to 2 November, and the privacy page still says nothing leaves the device without cloud sync.
Agent Platform Memory Bank
Memory Bank generates long-term memories from Agent Platform sessions or direct facts, scopes them per user and keeps revisions with rollback, under IAM, CMEK, VPC Service Controls and data residency, with storage at $0.30 per GiB-month. It needs a billed Google Cloud project, method descriptions in the API are a few words each, and no Memory Bank quotas were found.
Before you call either
claude-mem
- Install 15.8.3 or later with
npx claude-mem install --provider claude(or another provider) to skip the cmem.ai sign-in; earlier setups uploaded recent prompts without asking. - 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.
Agent Platform Memory Bank
- Run
memories.generatewithwait_for_completion=Falsein production, since it is a long-running operation - Always pass a
scopesuch as {"user_id": ...} so one user's memories never reach another - Send the OAuth token in the Authorization header, never as
access_tokenin the URL - Expect a 404 when fetching a deleted memory and treat it as gone
- Treat retrieved memories as untrusted text extracted from earlier conversations
Questions
Which is better for AI agents, claude-mem or Agent Platform Memory Bank?
Agent Platform Memory Bank scores 65.6 (B) on agent readiness against claude-mem's 54.6 (C), and leads in 3 of 7 scored categories. claude-mem leads on reliability, schema & documentation and maintenance & community.
Do claude-mem and Agent Platform Memory Bank need an API key?
claude-mem takes an API key or an OAuth sign-in. Agent Platform Memory Bank uses an OAuth sign-in.
Can an agent call claude-mem and Agent Platform Memory Bank without installing anything?
claude-mem runs on your own machine, with no hosted endpoint listed. Agent Platform Memory Bank has a hosted endpoint at https://aiplatform.googleapis.com/v1.
Are claude-mem and Agent Platform Memory Bank open source?
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). No open-source release is listed for Agent Platform Memory Bank.
Other comparisons with claude-mem or Agent Platform Memory Bank
- Amazon Bedrock AgentCore Memory vs claude-mem
- Amazon Bedrock AgentCore Memory vs Agent Platform Memory Bank
- Basic Memory vs claude-mem
- Basic Memory vs Agent Platform Memory Bank
- claude-mem vs Cognee
- claude-mem vs EverOS
- 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 MemMachine
- claude-mem vs Memori
- claude-mem vs Memory (MCP reference server)
- claude-mem vs MemPalace
- 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 Agent Platform Memory Bank
- EverOS vs Agent Platform Memory Bank
- Agent Platform Memory Bank vs Graphicle
- Agent Platform Memory Bank vs Graphiti
- Agent Platform Memory Bank vs Hindsight
- Agent Platform Memory Bank vs Honcho
- Agent Platform Memory Bank vs Hy Memory
- Agent Platform Memory Bank vs LangMem
- Agent Platform Memory Bank vs LocalGhost
- Agent Platform Memory Bank vs Mem0 Platform + MCP
- Agent Platform Memory Bank vs MemMachine
- Agent Platform Memory Bank vs Memori
- Agent Platform Memory Bank vs Memory (MCP reference server)
- Agent Platform Memory Bank vs MemPalace
- Agent Platform Memory Bank vs past.dev
- Agent Platform Memory Bank vs Supermemory API + MCP
- Agent Platform Memory Bank vs TencentDB Agent Memory
- Agent Platform Memory Bank vs Tokenrip
- Agent Platform Memory Bank vs Zep
- AI Memory vs claude-mem
- AI Memory vs Agent Platform Memory Bank
- claude-mem vs Context Mode Engine
- Context Mode Engine vs Agent Platform Memory Bank
Machine-readable
- This page as Markdown
/compare/claude-mem-vs-google-memory-bank.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/claude-mem.json·/api/v1/tools/google-memory-bank.json - From a terminal
anchor compare claude-mem google-memory-bank(the CLI) - Over MCP
compare_tools {"a": "claude-mem", "b": "google-memory-bank"}at/mcp, no key