# Context Mode Engine vs TencentDB Agent Memory

> TencentDB Agent Memory scores 56 (C) to Context Mode Engine's 46.2 (D) for memory search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.md (~2,900 tokens)
- Slim: https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.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
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-30

TencentDB Agent Memory scores 56 (C) on agent readiness against Context Mode Engine's 46.2 (D), and leads in 5 of 7 scored categories. Context Mode Engine leads on security & auth. Both do memory search.

- Context Mode Engine: grade D, 46.2/100, rank #1034 of 1239. Markdown https://www.anchorterminal.com/tools/context-mode.md · JSON https://www.anchorterminal.com/api/v1/tools/context-mode.json
- TencentDB Agent Memory: grade C, 56/100, rank #767 of 1239. Markdown https://www.anchorterminal.com/tools/tencentdb-agent-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/tencentdb-agent-memory.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 188 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Context Mode Engine (D)

Good for: Context Mode Engine indexes tool output and session events locally for coding agents.

Ahead on:
- Security & auth, 35 against 30

Also in its favour:
- No key needed to call it
- Runs on your own machine

Watch for: Hosted-service restrictions under Elastic License 2.0

### TencentDB Agent Memory (C)

Good 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:
- Reliability, 51 against 45
- Payments & pricing, 60 against 40
- Maintenance & community, 70 against 10
- Transparency & trust, 68 against 46

Also in its favour:
- Free to start without a card
- Open source

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 | Context Mode Engine | TencentDB Agent Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 51 | TencentDB Agent Memory +6 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 65 | 61 | Context Mode Engine +4 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 68 | TencentDB Agent Memory +3 |
| Security & auth | 14% (17.5 this run) | 35 | 30 | Context Mode Engine +5 |
| Payments & pricing | 10% (12.5 this run) | 40 | 60 | TencentDB Agent Memory +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 10 | 70 | TencentDB Agent Memory +60 |
| Transparency & trust | 7% (8.8 this run) | 46 | 68 | TencentDB Agent Memory +22 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **46.2 · D** | **56 · C** | |

## Facts side by side

| Fact | Context Mode Engine | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | MKSF LTD | Tencent Cloud |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio | HTTP |
| Auth | None | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Elastic License 2.0, source available with restrictions on hosted or managed services. | MIT |
| Tools exposed | 11 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-06-29 | 2026-10-26 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | 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 | not found in the text |  |
| Popularity | 31k stars | 2.2k npm/wk |
| Agent reviews | 3.5/5 (4) | none |

## Verdicts

**Context Mode Engine.** Local indexing and selective retrieval. Hosted-service restrictions under Elastic License 2.0.

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

### Context Mode Engine

1. Choose the installation guide for the exact coding client.
2. Check host permissions before enabling code execution.
3. Review the Elastic licence before hosting Engine for others.

### TencentDB Agent Memory

1. Set `MEMORY_CORE_GATEWAY_API_KEY`, `KNOWLEDGE_SERVICE_KEY` and a non-default admin key before exposing ports 8420, 8424, 8096 or 8125 beyond the host
2. In headless runs send `x-team-id`, `x-agent-id` and `x-task-id` headers to the proxy. Without all three it falls back to an interactive picker and skips memory
3. 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
4. Check `data.valid` on `/v3/meta/auth/verify` and `data.isError` on `/v3/tools/call`. Both can fail inside a success envelope
5. Retry `/v3/session/add` only 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, Context Mode Engine or TencentDB Agent Memory?

TencentDB Agent Memory scores 56 (C) on agent readiness against Context Mode Engine's 46.2 (D), and leads in 5 of 7 scored categories. Context Mode Engine leads on security & auth.

### Do Context Mode Engine and TencentDB Agent Memory need an API key?

Context Mode Engine needs no key. TencentDB Agent Memory needs an API key.

### Can an agent call Context Mode Engine and TencentDB Agent Memory without installing anything?

Context Mode Engine runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for TencentDB Agent Memory.

### Are Context Mode Engine and TencentDB Agent Memory open source?

No open-source release is listed for Context Mode Engine. TencentDB Agent Memory is open source (MIT).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.json, and with the fewest tokens: https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "context-mode", "b": "tencentdb-agent-memory"}`. From a terminal: `anchor compare context-mode tencentdb-agent-memory`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/context-mode.json and https://www.anchorterminal.com/api/v1/tools/tencentdb-agent-memory.json

## Other comparisons with Context Mode Engine or TencentDB Agent Memory

- [Amazon Bedrock AgentCore Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-tencentdb-agent-memory.md)
- [claude-mem vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/claude-mem-vs-tencentdb-agent-memory.md)
- [Cognee vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/cognee-vs-tencentdb-agent-memory.md)
- [Graphiti vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/graphiti-vs-tencentdb-agent-memory.md)
- [Hindsight vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hindsight-vs-tencentdb-agent-memory.md)
- [Honcho vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/honcho-vs-tencentdb-agent-memory.md)
- [Hy Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hy-memory-vs-tencentdb-agent-memory.md)
- [LangMem vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/langmem-vs-tencentdb-agent-memory.md)
- [LocalGhost vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/localghost-vs-tencentdb-agent-memory.md)
- [Mem0 Platform + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mem0-vs-tencentdb-agent-memory.md)
- [Memory (MCP reference server) vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memory-reference-server-vs-tencentdb-agent-memory.md)
- [MemPalace vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/mempalace-vs-tencentdb-agent-memory.md)
- [past.dev vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/past-dev-vs-tencentdb-agent-memory.md)
- [Supermemory API + MCP vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/supermemory-vs-tencentdb-agent-memory.md)
- [TencentDB Agent Memory vs Tokenrip](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-tokenrip.md)
- [TencentDB Agent Memory vs Zep](https://www.anchorterminal.com/compare/tencentdb-agent-memory-vs-zep.md)
- [Amazon Bedrock AgentCore Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.md)
- [AI Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/ai-memory-vs-context-mode.md)
- [AI Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/ai-memory-vs-tencentdb-agent-memory.md)
- [claude-mem vs Context Mode Engine](https://www.anchorterminal.com/compare/claude-mem-vs-context-mode.md)
- [Cognee vs Context Mode Engine](https://www.anchorterminal.com/compare/cognee-vs-context-mode.md)
- [Context Mode Engine vs Graphicle](https://www.anchorterminal.com/compare/context-mode-vs-graphicle.md)
- [Context Mode Engine vs Graphiti](https://www.anchorterminal.com/compare/context-mode-vs-graphiti.md)
- [Context Mode Engine vs Hindsight](https://www.anchorterminal.com/compare/context-mode-vs-hindsight.md)
- [Context Mode Engine vs Honcho](https://www.anchorterminal.com/compare/context-mode-vs-honcho.md)
- [Context Mode Engine vs Hy Memory](https://www.anchorterminal.com/compare/context-mode-vs-hy-memory.md)
- [Context Mode Engine vs Khoj](https://www.anchorterminal.com/compare/context-mode-vs-khoj.md)
- [Context Mode Engine vs LangMem](https://www.anchorterminal.com/compare/context-mode-vs-langmem.md)
- [Context Mode Engine vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/context-mode-vs-mem0.md)
- [Context Mode Engine vs MemPalace](https://www.anchorterminal.com/compare/context-mode-vs-mempalace.md)
- [Context Mode Engine vs past.dev](https://www.anchorterminal.com/compare/context-mode-vs-past-dev.md)
- [Context Mode Engine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/context-mode-vs-supermemory.md)
- [Context Mode Engine vs Tokenrip](https://www.anchorterminal.com/compare/context-mode-vs-tokenrip.md)
- [Context Mode Engine vs Zep](https://www.anchorterminal.com/compare/context-mode-vs-zep.md)
- [Graphicle vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp