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

SupermemoryCodebase Memory MCP

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

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	SupermemoryShortlist candidate	Codebase Memory MCPMCP100 Recommended
Task fit
Best for	Users who want persistent cross-session memory/recall with explicit project scoping.	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	Privacy-sensitive workflows that should not persist conversation/project memory outside the client.	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when	Do not store secrets or sensitive personal/project data unless Supermemory retention/project boundaries meet your requirements.	The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	First-party MCP endpoint:https: · Publisher source ↗	First-party MCP 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	44,904 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	No reliable download data	28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z
Shared repository stars	31,345 Shared repository stars (not MCP-specific) · checked 2026-10-21	Not documented
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	OAuth is the default; API key/Bearer authentication is an alternative.	local stdio; no remote auth needed
Cost	Supermemory plan/API limits and model/provider costs apply.	none beyond local resources
Permissions	Can add/read persistent memories available to the authorized account/project.	reads indexed source/project data; installer writes supported agent/editor configs/hooks
Data handling	Submitted memories are intentionally persisted by the Supermemory service; project scoping and retention are therefore central privacy controls.	local processing; current docs state no source/index/query/env/telemetry upload
Limitations
Tradeoffs	Promising signal, but it ranks below the current Recommended/Shortlist admission cohort on maturity, uniqueness, publisher trust, security clarity, or MCP-native evidence.	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	Intentional persistent storage can retain sensitive context beyond the current session.	latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy
Evidence date
Editorial review	2026-10-21	2026-09-23
Candidate evidence	2026-10-21T00:00:00Z	2026-09-25T18:35:00Z

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

Read the evidence method →