# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cognee-vs-supermemory
- Markdown: https://www.anchorterminal.com/compare/cognee-vs-supermemory.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/compare/cognee-vs-supermemory.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cognee-vs-supermemory.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

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.

- Cognee: grade C, 54.6/100, rank #320 of 452. Markdown https://www.anchorterminal.com/tools/cognee.md · JSON https://www.anchorterminal.com/api/v1/tools/cognee.json
- Supermemory API + MCP: grade B, 63.6/100, rank #201 of 452. Markdown https://www.anchorterminal.com/tools/supermemory.md · JSON https://www.anchorterminal.com/api/v1/tools/supermemory.json

## 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

| Category | Weight | Cognee | Supermemory API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 65 | Supermemory API + MCP +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 85 | even |
| Agent ergonomics | 13% (16.2 this run) | 59 | 73 | Supermemory API + MCP +14 |
| Security & auth | 14% (17.5 this run) | 39 | 54 | Supermemory API + MCP +15 |
| Payments & pricing | 10% (12.5 this run) | 35 | 30 | Cognee +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 85 | Supermemory API + MCP +3 |
| Transparency & trust | 7% (8.8 this run) | 67 | 49 | Cognee +18 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **54.6 · C** | **63.6 · B** | |

## Facts side by side

| Fact | Cognee | Supermemory API + MCP |
| --- | --- | --- |
| Kind | Model platform | HTTP API |
| Vendor | Cognee | Supermemory |
| Hosted endpoint | `https://<tenant>.aws.cognee.ai/api/v1` | `https://api.supermemory.ai` |
| Transports | HTTP, stdio, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 7 | 8 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-29 | 2026-09-21 |
| Popularity | 31k stars, 21k PyPI/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | 3/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

- [Cognee vs Graphiti](https://www.anchorterminal.com/compare/cognee-vs-graphiti.md)
- [Cognee vs Hindsight](https://www.anchorterminal.com/compare/cognee-vs-hindsight.md)
- [Cognee vs Honcho](https://www.anchorterminal.com/compare/cognee-vs-honcho.md)
- [Cognee vs LocalGhost](https://www.anchorterminal.com/compare/cognee-vs-localghost.md)
- [Cognee vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/cognee-vs-mem0.md)
- [Cognee vs Zep](https://www.anchorterminal.com/compare/cognee-vs-zep.md)
- [Graphiti vs Supermemory API + MCP](https://www.anchorterminal.com/compare/graphiti-vs-supermemory.md)
- [Hindsight vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hindsight-vs-supermemory.md)
- [Honcho vs Supermemory API + MCP](https://www.anchorterminal.com/compare/honcho-vs-supermemory.md)
- [LocalGhost vs Supermemory API + MCP](https://www.anchorterminal.com/compare/localghost-vs-supermemory.md)
- [Mem0 Platform + MCP vs Supermemory API + MCP](https://www.anchorterminal.com/compare/mem0-vs-supermemory.md)
- [Supermemory API + MCP vs Zep](https://www.anchorterminal.com/compare/supermemory-vs-zep.md)