Sign in

Head to head · Memory search · October 2026 research run

Context Mode Engine vs 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. Both do memory search.

Best memory layers for AI agents · All 188 memory comparisons

Context Mode EngineMKSF LTD · MCP server D46.2/100#1033 of 1238 TencentDB Agent MemoryTencent Cloud · HTTP API C56/100#766 of 1238

Which one, for what

Context Mode Engine D

Best 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

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

  • 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

CategoryWeight this runContext Mode EngineTencentDB Agent MemoryEdge
Reliability16%204551TencentDB Agent Memory +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26561Context Mode Engine +4
Agent ergonomics13%16.26568TencentDB Agent Memory +3
Security & auth14%17.53530Context Mode Engine +5
Payments & pricing10%12.54060TencentDB Agent Memory +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81070TencentDB Agent Memory +60
Transparency & trust7%8.84668TencentDB Agent Memory +22
Negative events≤1500
TotalD 46.2/100C 56/100

Facts side by side

FactContext Mode EngineTencentDB Agent Memory
KindMCP serverHTTP API
VendorMKSF LTDTencent Cloud
Hosted endpointno (local only)no (local only)
TransportsstdioHTTP
AuthNoneAPI key
PricingFreemiumFree
x402nono
LicenceElastic License 2.0, source available with restrictions on hosted or managed services.MIT
Tools exposed11none
Read-only variant documentednono
llms.txtnono
Last release2026-06-292026-10-26
Terms last updatedno date givenno document linked
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity31k stars2.2k npm/wk
Agent reviews3.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).

Other comparisons with Context Mode Engine or TencentDB Agent Memory

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report