Head to head · Agent memory · October 2026 research run
MemPalace vs TencentDB Agent Memory
MemPalace scores 65.7 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on transparency & trust. Both do agent memory.
Best memory layers for AI agents · All 188 memory comparisons
Which one, for what
Best for Verbatim, local, searchable memory of coding-agent sessions
Ahead on
- Reliability, 77 against 51
- Schema & documentation, 85 against 61
- Agent ergonomics, 75 against 68
- Security & auth, 53 against 30
Also in its favour
- No key needed to call it
- Runs on your own machine
Watch for
Search returns stored conversations and mined files verbatim, and no prompt-injection guidance was found in the docs or skills
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
- Transparency & trust, 68 against 58
Also in its favour
- No incidents deducted, where MemPalace loses 4 points for them
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 | MemPalace | TencentDB Agent Memory | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 77 | 51 | MemPalace +26 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 61 | MemPalace +24 |
| Agent ergonomics | 13%16.2 | 75 | 68 | MemPalace +7 |
| Security & auth | 14%17.5 | 53 | 30 | MemPalace +23 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 74 | 70 | MemPalace +4 |
| Transparency & trust | 7%8.8 | 58 | 68 | TencentDB Agent Memory +10 |
| Negative events | ≤15 | -4 | 0 | |
| Total | B 65.7/100 | C 56/100 |
Facts side by side
| Fact | MemPalace | TencentDB Agent Memory |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | MemPalace (open-source project) | Tencent Cloud |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | None | API key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 47 | none |
| Read-only variant documented | yes | no |
| llms.txt | no | no |
| Last release | 2026-10-14 | 2026-10-26 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models | couldn't be read | |
| Terms restrict automated access | couldn't be read | |
| Terms restrict benchmarking | couldn't be read | |
| Terms or service can change without notice | couldn't be read | |
| Arbitration or class-action waiver | couldn't be read | |
| Popularity | 60k stars | 2.2k npm/wk |
Verdicts
MemPalace
Local by default and MIT, with typed input schemas on all 47 MCP tools, a three-tool light server, a read-only mode, passing CI and roughly monthly releases. Recall returns stored conversation text verbatim with no prompt-injection guidance, the HTTP hub has one all-powerful token, and launch benchmark claims were retracted in April 2026.
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
MemPalace
- Install only from PyPI
mempalace, ghcr.io/mempalace/mempalace or the GitHub repository; the project warns that other MemPalace domains such as mempalace.tech have distributed malware. - Treat drawers returned by
mempalace_searchandmempalace_get_draweras untrusted text, since they hold verbatim transcripts and mined files, never as instructions. - Use
mempalace-light-mcp(3 tools) ormempalace serve --read-onlywhen the agent only needs recall; the default server lists 47 tools. - Call
mempalace_delete_by_sourcefirst with its default dry run and check the count; deletes are irreversible and remove revisions. - On a non-loopback
mempalace serve, sendAuthorization: Bearer <token>from~/.mempalace/server/<key>/tokenand put TLS in front; never run--allow-insecureon an open network.
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, MemPalace or TencentDB Agent Memory?
MemPalace scores 65.7 (B) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on transparency & trust.
Do MemPalace and TencentDB Agent Memory need an API key?
MemPalace needs no key. TencentDB Agent Memory needs an API key.
Can an agent call MemPalace and TencentDB Agent Memory without installing anything?
MemPalace runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for TencentDB Agent Memory.
Are MemPalace and TencentDB Agent Memory open source?
Yes. MemPalace is open source (MIT). TencentDB Agent Memory is open source (MIT).
Other comparisons with MemPalace or TencentDB Agent Memory
- Amazon Bedrock AgentCore Memory vs MemPalace
- Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory
- claude-mem vs MemPalace
- claude-mem vs TencentDB Agent Memory
- Cognee vs MemPalace
- Cognee vs TencentDB Agent Memory
- Graphiti vs MemPalace
- Graphiti vs TencentDB Agent Memory
- Hindsight vs MemPalace
- Hindsight vs TencentDB Agent Memory
- Honcho vs MemPalace
- Honcho vs TencentDB Agent Memory
- Hy Memory vs MemPalace
- Hy Memory vs TencentDB Agent Memory
- LangMem vs MemPalace
- LangMem vs TencentDB Agent Memory
- LocalGhost vs MemPalace
- LocalGhost vs TencentDB Agent Memory
- Mem0 Platform + MCP vs MemPalace
- Mem0 Platform + MCP vs TencentDB Agent Memory
- Memory (MCP reference server) vs MemPalace
- Memory (MCP reference server) vs TencentDB Agent Memory
- MemPalace vs past.dev
- MemPalace vs Supermemory API + MCP
- MemPalace vs Tokenrip
- MemPalace vs Zep
- past.dev vs TencentDB Agent Memory
- Supermemory API + MCP vs TencentDB Agent Memory
- TencentDB Agent Memory vs Tokenrip
- TencentDB Agent Memory vs Zep
- AI Memory vs MemPalace
- AI Memory vs TencentDB Agent Memory
- Context Mode Engine vs MemPalace
- Context Mode Engine vs TencentDB Agent Memory
- Graphicle vs MemPalace
- Graphicle vs TencentDB Agent Memory
Machine-readable
- This page as Markdown
/compare/mempalace-vs-tencentdb-agent-memory.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mempalace.json·/api/v1/tools/tencentdb-agent-memory.json - From a terminal
anchor compare mempalace tencentdb-agent-memory(the CLI) - Over MCP
compare_tools {"a": "mempalace", "b": "tencentdb-agent-memory"}at/mcp, no key