# Graphiti vs Supermemory API + MCP

> Supermemory API + MCP has a score of 63.6 (B) against Graphiti's 53.3 (D). Both do memory store. The largest gap is security & auth, 31 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/graphiti-vs-supermemory
- Markdown: https://www.anchorterminal.com/compare/graphiti-vs-supermemory.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/compare/graphiti-vs-supermemory.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/graphiti-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 Graphiti's 53.3 (D). Both do memory store. The largest gap is security & auth, 31 points.

- Graphiti: grade D, 53.3/100, rank #333 of 452. Markdown https://www.anchorterminal.com/tools/graphiti.md · JSON https://www.anchorterminal.com/api/v1/tools/graphiti.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 Graphiti for payments & pricing (+30), transparency & trust (+22).

Pick Supermemory API + MCP for reliability (+15), schema & documentation (+14), agent ergonomics (+22), security & auth (+31), maintenance & community (+20).

## Score by category

| Category | Weight | Graphiti | 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) | 71 | 85 | Supermemory API + MCP +14 |
| Agent ergonomics | 13% (16.2 this run) | 51 | 73 | Supermemory API + MCP +22 |
| Security & auth | 14% (17.5 this run) | 23 | 54 | Supermemory API + MCP +31 |
| Payments & pricing | 10% (12.5 this run) | 60 | 30 | Graphiti +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 65 | 85 | Supermemory API + MCP +20 |
| Transparency & trust | 7% (8.8 this run) | 71 | 49 | Graphiti +22 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.3 · D** | **63.6 · B** | |

## Facts side by side

| Fact | Graphiti | Supermemory API + MCP |
| --- | --- | --- |
| Kind | Agent framework | HTTP API |
| Vendor | Zep | Supermemory |
| Hosted endpoint | no (local only) | `https://api.supermemory.ai` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 13 | 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-08 | 2026-09-21 |
| Popularity | 29k stars, 151k PyPI/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |

## Verdicts

**Graphiti.** Apache-2.0, with FalkorDB, Neo4j or Amazon Neptune as the store. Every add runs LLM extraction, so ingestion costs tokens and time.

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

### Graphiti

1. Set OPENAI_API_KEY (or another provider's key) and MODEL_NAME before starting the MCP server
2. Use search_memory_facts for facts and search_nodes for entities instead of reading whole episodes
3. Never call clear_graph to fix one fact. Use delete_episode or delete_entity_edge
4. Pass group_ids on every search and add so one user's graph doesn't leak into another's
5. Call get_status to check the database connection before a long ingest

### 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 Graphiti or Supermemory API + MCP

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