Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Mem0 MCPCodebase Memory

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

AWS Documentation MCPMCP100 SelectedAsana MCPMCP100 SelectedAtlassian Remote MCPMCP100 SelectedAzure MCP ServerMCP100 SelectedCanva Dev MCPMCP100 SelectedChrome DevTools MCPMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Mem0 MCPWatchlist candidate	Codebase MemoryMCP100 Selected
Task fit
Best for	Persistent agent memory backed by Mem0 Platform Users who want a hosted MCP endpoint instead of running the archived local server	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	Sensitive memory stores without clear retention/deletion/account controls Workflows where the AI should never persist user data	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when	You cannot define acceptable memory retention and deletion policy You do not trust the AI client with add/update/delete memory permissions	The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	First-party MCP Mem0 · Publisher source ↗	Community implementation io.github.DeusData · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Aug 14, 2026
Popularity evidence
GitHub stars	Not documented	38,935 GitHub stars · checked 2026-08-14T18:46:26.000Z
Package downloads / 30 days	No reliable download data	28,015 package downloads / 30 days · checked 2026-09-08
External adoption evidence	Not documented	npm: package downloads: 28,015Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Requires a Mem0 Platform account/API key for the hosted MCP setup.	No authentication or API key is documented for local stdio. CBM_ALLOWED_ROOT is an optional filesystem containment control; no containment is imposed when it is unset.
Cost	Mem0 Platform pricing/limits apply.	The MIT-licensed native software lists no service fee. Local storage and package-manager costs are separate.
Permissions	Tools can add, search, retrieve, update, and delete long-term memories within the Mem0 account scope.	Indexes repositories, queries code and graphs, performs architecture and impact analysis, manages ADRs and watchers, deletes projects, and writes agent configuration, instruction, Skill, and hook files.
Data handling	User/agent memory content is stored in Mem0 Platform and may persist across sessions until updated/deleted according to the account's controls.	The publisher says processing is local and code does not leave the machine. Indexes, embeddings, memories, SQLite data, and logs persist under the local CBM cache directory.
Limitations
Tradeoffs	Cloud hosting simplifies setup but introduces a third-party data boundary Memory writes can create durable effects that outlive the current session	Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed. Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk context	High for sensitive contexts. Persistent memory can store private content and delete/update operations are durable; tenant, retention, audit, and revocation controls need periodic review.	Indexing can capture sensitive files, while persistent graph data and installer/configuration writes expand local exposure. Set CBM_ALLOWED_ROOT, protect the cache, and use explicit project paths.
Evidence date
Editorial review	2026-09-11	2026-09-05
Candidate evidence	2026-09-11T00:00:00.000Z	2026-09-05T00:00:00.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →