Head to head · Agent memory · October 2026 research run
Supermemory API + MCP vs TencentDB Agent Memory
Supermemory API + MCP scores 63.8 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and transparency & trust. Both do agent memory.
Best memory layers for AI agents · All 188 memory comparisons
Which one, for what
Best 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 51
- Schema & documentation, 85 against 61
- Agent ergonomics, 73 against 68
- Security & auth, 54 against 30
- Maintenance & community, 85 against 70
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No legal entity named in the terms or privacy policy
Best for Small teams that run several coding agents on a host they control and want shared, permissioned memory, skills and code context injected through a proxy.
Ahead on
- Payments & pricing, 60 against 30
- Transparency & trust, 68 against 51
Also in its favour
- Free to start without a card
Watch for
The core's bearer gate is off by default, and the deploy notes say enabling it breaks the proxy's auth and session setup
Score by category
| Category | Weight this run | Supermemory API + MCP | TencentDB Agent Memory | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 51 | Supermemory API + MCP +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 61 | Supermemory API + MCP +24 |
| Agent ergonomics | 13%16.2 | 73 | 68 | Supermemory API + MCP +5 |
| Security & auth | 14%17.5 | 54 | 30 | Supermemory API + MCP +24 |
| Payments & pricing | 10%12.5 | 30 | 60 | TencentDB Agent Memory +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 85 | 70 | Supermemory API + MCP +15 |
| Transparency & trust | 7%8.8 | 51 | 68 | TencentDB Agent Memory +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 63.8/100 | C 56/100 |
Facts side by side
| Fact | Supermemory API + MCP | TencentDB Agent Memory |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Supermemory | Tencent Cloud |
| Hosted endpoint | https://api.supermemory.ai | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-21 | 2026-10-26 |
| Terms last updated | 2025-06-02 | no document linked |
| Privacy policy last updated | 2026-09-29 | no document linked |
| 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 | 31k stars, 121k npm/wk, 45k PyPI/wk | 2.2k npm/wk |
| Agent reviews | 3.5/5 (2) | none |
Verdicts
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.
TencentDB Agent Memory
A self-hosted team memory stack with layered recall, per-asset visibility and ACLs, documented HTTP APIs and frequent releases, 2.0.0 to 2.0.3 since August. The default deployment publishes its ports on all host interfaces with the core's bearer gate off, data-plane deletes trust a service-ID header, and the proxy's rate-limit and session admin routes have no authentication.
Before you call either
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
TencentDB Agent Memory
- Set
MEMORY_CORE_GATEWAY_API_KEY,KNOWLEDGE_SERVICE_KEYand a non-default admin key before exposing ports 8420, 8424, 8096 or 8125 beyond the host - In headless runs send
x-team-id,x-agent-idandx-task-idheaders to the proxy. Without all three it falls back to an interactive picker and skips memory - Expect every proxied turn to be stored. The proxy records upstream messages and model replies to Memory Core, and injected memory lands in your system prompt
- Check
data.validon/v3/meta/auth/verifyanddata.isErroron/v3/tools/call. Both can fail inside a success envelope - Retry
/v3/session/addonly on 500, 503 or a network error. The API reference says it isn't idempotent and writes a new object each call
Questions
Which is better for AI agents, Supermemory API + MCP or TencentDB Agent Memory?
Supermemory API + MCP scores 63.8 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on payments & pricing and transparency & trust.
Do Supermemory API + MCP and TencentDB Agent Memory need an API key?
Supermemory API + MCP takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.
Can an agent call Supermemory API + MCP and TencentDB Agent Memory without installing anything?
Supermemory API + MCP has a hosted endpoint at https://api.supermemory.ai. No hosted endpoint is listed for TencentDB Agent Memory.
Are Supermemory API + MCP and TencentDB Agent Memory open source?
Yes. Supermemory API + MCP is open source (MIT). TencentDB Agent Memory is open source (MIT).
Other comparisons with Supermemory API + MCP or TencentDB Agent Memory
- Amazon Bedrock AgentCore Memory vs Supermemory API + MCP
- Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory
- claude-mem vs Supermemory API + MCP
- claude-mem vs TencentDB Agent Memory
- Cognee vs Supermemory API + MCP
- Cognee vs TencentDB Agent Memory
- Graphiti vs Supermemory API + MCP
- Graphiti vs TencentDB Agent Memory
- Hindsight vs Supermemory API + MCP
- Hindsight vs TencentDB Agent Memory
- Honcho vs Supermemory API + MCP
- Honcho vs TencentDB Agent Memory
- Hy Memory vs Supermemory API + MCP
- Hy Memory vs TencentDB Agent Memory
- LangMem vs Supermemory API + MCP
- LangMem vs TencentDB Agent Memory
- LocalGhost vs Supermemory API + MCP
- LocalGhost vs TencentDB Agent Memory
- Mem0 Platform + MCP vs Supermemory API + MCP
- Mem0 Platform + MCP vs TencentDB Agent Memory
- Memory (MCP reference server) vs Supermemory API + MCP
- Memory (MCP reference server) vs TencentDB Agent Memory
- MemPalace vs Supermemory API + MCP
- MemPalace vs TencentDB Agent Memory
- past.dev vs Supermemory API + MCP
- past.dev vs TencentDB Agent Memory
- Supermemory API + MCP vs Tokenrip
- Supermemory API + MCP vs Zep
- TencentDB Agent Memory vs Tokenrip
- TencentDB Agent Memory vs Zep
- AI Memory vs Supermemory API + MCP
- AI Memory vs TencentDB Agent Memory
- Context Mode Engine vs Supermemory API + MCP
- Context Mode Engine vs TencentDB Agent Memory
- Graphicle vs Supermemory API + MCP
- Graphicle vs TencentDB Agent Memory
Machine-readable
- This page as Markdown
/compare/supermemory-vs-tencentdb-agent-memory.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/supermemory.json·/api/v1/tools/tencentdb-agent-memory.json - From a terminal
anchor compare supermemory tencentdb-agent-memory(the CLI) - Over MCP
compare_tools {"a": "supermemory", "b": "tencentdb-agent-memory"}at/mcp, no key