Head to head · Memory store · October 2026 research run
LangMem vs Supermemory API + MCP
Supermemory API + MCP scores 63.6 (B) on agent readiness against LangMem's 47.9 (D), and leads in 5 of 7 scored categories. LangMem leads on payments & pricing and transparency & trust. Both do memory store.
Which one, for what
LangMem D
Good for Teams already on LangGraph that want memory tools and background extraction over a store they run.
Ahead on
- Payments & pricing, 60 against 30
- Transparency & trust, 59 against 49
Also in its favour
- No key needed to call it
Watch for
The newest PyPI release, 0.0.30, is from 27 October 2025, and every commit to src on main is older than that
Good for Apps that need user memory and document search over the same data, and for multi-tenant products that want a key per user.
Ahead on
- Reliability, 65 against 32
- Schema & documentation, 85 against 55
- Agent ergonomics, 73 against 66
- Security & auth, 54 against 45
- Maintenance & community, 85 against 15
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No legal entity named in the terms or privacy policy
Score by category
| Category | Weight this run | LangMem | Supermemory API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 32 | 65 | Supermemory API + MCP +33 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 55 | 85 | Supermemory API + MCP +30 |
| Agent ergonomics | 13%16.2 | 66 | 73 | Supermemory API + MCP +7 |
| Security & auth | 14%17.5 | 45 | 54 | Supermemory API + MCP +9 |
| Payments & pricing | 10%12.5 | 60 | 30 | LangMem +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 15 | 85 | Supermemory API + MCP +70 |
| Transparency & trust | 7%8.8 | 59 | 49 | LangMem +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 47.9 · D | 63.6 · B |
Facts side by side
| Fact | LangMem | Supermemory API + MCP |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | LangChain | Supermemory |
| Hosted endpoint | no (local only) | https://api.supermemory.ai |
| Transports | HTTP, Streamable HTTP | |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2025-10-27 | 2026-09-21 |
| Terms last updated | no document linked | 2025-06-02 |
| Privacy policy last updated | no document linked | 2026-09-29 |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | yes | |
| Popularity | 1.7k stars, 214k PyPI/wk | 31k stars, 121k npm/wk, 45k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |
Verdicts
LangMem
Two compact, typed memory tools and a background extraction manager work with any LangGraph store, under the MIT licence with nothing to buy. The newest PyPI release, 0.0.30, dates from 27 October 2025. The repository has no changelog, tags or test workflow, and 23 of 54 open issues have no reply.
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
LangMem
- Pass a store with an embedding index (
index={"dims": 1536, "embed": "openai:text-embedding-3-small"}), orsearch_memorycannot rank by meaning - Use a database-backed store such as
AsyncPostgresStorefor anything that must survive a restart.InMemoryStoreloses everything - Put a per-user placeholder in the namespace and set it in
config["configurable"]on every call, or users share one memory space - Send the memory
idwithupdateanddelete, and never withcreate. A retriedcreatewrites a duplicate under a new UUID - Run on Python 3.11 or later.
src/langmem/knowledge/extraction.pyusestyping.NotRequired, which Python 3.10 lacks
Supermemory API + MCP
- Use one stable
containerTagper user and acustomIdper session - Poll the document until
statusisdonebefore searching for what you just added - Treat a 402 on search or profile as out of credit, not as a bug
- Run the prompt-based mass forget with
dryRunfirst - Call who_am_i on the MCP to see which spaces you can write to before adding
Questions
Which is better for AI agents, LangMem or Supermemory API + MCP?
Supermemory API + MCP scores 63.6 (B) on agent readiness against LangMem's 47.9 (D), and leads in 5 of 7 scored categories. LangMem leads on payments & pricing and transparency & trust.
Can an agent call LangMem and Supermemory API + MCP without installing anything?
No hosted endpoint is listed for LangMem. Supermemory API + MCP has a hosted endpoint at https://api.supermemory.ai.
Are LangMem and Supermemory API + MCP open source?
Yes. LangMem is open source (MIT). Supermemory API + MCP is open source (MIT).
Other comparisons with LangMem or Supermemory API + MCP
- Amazon Bedrock AgentCore Memory vs LangMem
- Amazon Bedrock AgentCore Memory vs Supermemory API + MCP
- Cognee vs LangMem
- Cognee vs Supermemory API + MCP
- Graphiti vs LangMem
- Graphiti vs Supermemory API + MCP
- Hindsight vs LangMem
- Hindsight vs Supermemory API + MCP
- Honcho vs LangMem
- Honcho vs Supermemory API + MCP
- LangMem vs LocalGhost
- LangMem vs Mem0 Platform + MCP
- LangMem vs Zep
- LocalGhost vs Supermemory API + MCP
- Mem0 Platform + MCP vs Supermemory API + MCP
- Supermemory API + MCP vs Zep
Machine-readable
- This page as Markdown
/compare/langmem-vs-supermemory.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/langmem.json·/api/v1/tools/supermemory.json - From a terminal
anchor compare langmem supermemory(the CLI) - Over MCP
compare_tools {"a": "langmem", "b": "supermemory"}at/mcp, no key