Get an audit

Head to head · Memory store · October 2026 research run

Cognee vs Supermemory API + MCP

Supermemory API + MCP has a score of 63.6 (B) against Cognee's 54.6 (C). Both do memory store. The largest gap is transparency & trust, 18 points.

CogneeCognee · Model platform C54.6/100#320 of 452 Supermemory API + MCPSupermemory · HTTP API B63.6/100#201 of 452

Which one, for what

Pick Cognee for

  • payments & pricing (+5)
  • transparency & trust (+18)

Pick Supermemory API + MCP for

  • reliability (+15)
  • agent ergonomics (+14)
  • security & auth (+15)

Score by category

CategoryWeight this runCogneeSupermemory API + MCPEdge
Reliability16%205065Supermemory API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28585even
Agent ergonomics13%16.25973Supermemory API + MCP +14
Security & auth14%17.53954Supermemory API + MCP +15
Payments & pricing10%12.53530Cognee +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88285Supermemory API + MCP +3
Transparency & trust7%8.86749Cognee +18
Negative events≤15-30
Total54.6 · C63.6 · B

Facts side by side

FactCogneeSupermemory API + MCP
KindModel platformHTTP API
VendorCogneeSupermemory
Hosted endpointhttps://<tenant>.aws.cognee.ai/api/v1https://api.supermemory.ai
TransportsHTTP, stdio, SSE (legacy)HTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0MIT
Tools exposed78
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-292026-09-21
Popularity31k stars, 21k PyPI/wk31k stars, 121k npm/wk, 45k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

Verdicts

Cognee

Apache-2.0 library, REST server and MCP server, all self-hostable, with local models and no LLM key since 1.6.0. No status page, rate limits, SLA or SOC 2 for Cloud, and Cloud runs in AWS us-east-1 with no EU region.

Supermemory API + MCP

8-tool hosted MCP with OAuth and per-space read or write permission. No legal entity named in the terms or privacy policy.

Before you call either

Cognee

  1. Use remember, recall and forget. The older cognify, search and delete MCP tools are gone
  2. Always include /api/v1 in REST paths
  3. Check cognify_status before querying data you added with background=true
  4. Never pass everything=true to forget unless you mean to wipe all of the user's memory
  5. Set a client timeout on Cloud calls and treat HTTP 402 as an empty balance, since an empty balance has also shown up as hangs

Supermemory API + MCP

  1. Use one stable containerTag per user and a customId per session
  2. Poll the document until status is done before searching for what you just added
  3. Treat a 402 on search or profile as out of credit, not as a bug
  4. Run the prompt-based mass forget with dryRun first
  5. Call who_am_i on the MCP to see which spaces you can write to before adding

Other comparisons with Cognee or Supermemory API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report