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.
| Evidence field | CogneeShortlist candidate | Codebase Memory MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP github:topoteretes · 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 | 1,288 package downloads / 30 days · checked 2026-10-21 | 28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z |
| Shared repository stars | 32,633 Shared repository stars (not MCP-specific) · checked 2026-10-21 | Not documented |
| External adoption evidence | Not documented |
|
| 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 | Cloud-backed configuration can use Cognee API key headers; self-hosted HTTP deployments can use documented Bearer-token/auth modes. | local stdio; no remote auth needed |
| Cost | Open-source/self-hosted infrastructure or Cognee cloud plan plus model/provider costs may apply. | none beyond local resources |
| Permissions | Can ingest, persist, query and in some modes delete/manage memory datasets according to deployment credentials. | reads indexed source/project data; installer writes supported agent/editor configs/hooks |
| Data handling | Content supplied to Cognee can be persisted in graph/vector/storage backends; retention and tenant isolation depend on the deployment. | local processing; current docs state no source/index/query/env/telemetry upload |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Persistent memory can retain sensitive project/user information beyond the current conversation. | 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 →