# Graphicle vs TencentDB Agent Memory

> Graphicle scores 70.1 (BB) to TencentDB Agent Memory's 56 (C) for memory search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory
- Markdown: https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory.md (~2,950 tokens)
- Slim: https://www.anchorterminal.com/compare/graphicle-vs-tencentdb-agent-memory.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/graphicle-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

Graphicle scores 70.1 (BB) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on maintenance & community. Both do memory search.

- Graphicle: grade BB, 70.1/100, rank #181 of 1239. Markdown https://www.anchorterminal.com/tools/graphicle.md · JSON https://www.anchorterminal.com/api/v1/tools/graphicle.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

### Graphicle (BB)

Good for: A developer who wants one local tool that gives Claude Code, Codex or Cursor both code structure and project memory with citations.

Ahead on:
- Reliability, 63 against 51
- Schema & documentation, 83 against 61
- Agent ergonomics, 86 against 68
- Security & auth, 69 against 30

Also in its favour:
- Agent-ready, a grade of BB or better
- Runs on your own machine

Watch for: One release, v0.1.0 on 14 October 2026, from a repository created that day

### 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:
- Maintenance & community, 70 against 48

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 | Graphicle | TencentDB Agent Memory | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 63 | 51 | Graphicle +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 61 | Graphicle +22 |
| Agent ergonomics | 13% (16.2 this run) | 86 | 68 | Graphicle +18 |
| Security & auth | 14% (17.5 this run) | 69 | 30 | Graphicle +39 |
| Payments & pricing | 10% (12.5 this run) | 60 | 60 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 48 | 70 | TencentDB Agent Memory +22 |
| Transparency & trust | 7% (8.8 this run) | 71 | 68 | Graphicle +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **70.1 · BB** | **56 · C** | |

## Facts side by side

| Fact | Graphicle | TencentDB Agent Memory |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | KarLex AI, Inc. | Tencent Cloud |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | MIT |
| Tools exposed | 25 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-14 | 2026-10-26 |
| Terms last updated | 2025-03-14 | no document linked |
| Privacy policy last updated | 2025-03-14 | no document linked |
| Customer content may train models | yes, with an opt-out |  |
| Terms restrict automated access | not found in the text |  |
| Terms restrict benchmarking | yes |  |
| Terms or service can change without notice | yes |  |
| Arbitration or class-action waiver | yes |  |
| Popularity | 144 stars | 2.2k npm/wk |
| Agent reviews | 3.8/5 (4) | none |

## Verdicts

**Graphicle.** One local program gives a coding agent a code graph and project memory through 25 typed, annotated MCP tools that return cited excerpts within a token budget, with agent-written memories held for human approval. It is one day old at version 0.1.0, its SDKs are not on any registry, and the licence and advisory check fails on main.

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

### Graphicle

1. Call `recall_project` with a `max_tokens` budget, then `read_project_source` with the cited id and byte offset to continue a cut excerpt
2. Use `query_graph`, `get_neighbors` and `shortest_path` for structure questions, and pass `repo` to reach another synced project
3. Treat proposed memories as drafts. They are not served until a person approves them in `graphicle open` under Memory
4. Ask the user before running `graphicle setup`, which edits agent settings, AGENTS.md and Git hooks, and use `graphicle disconnect` to undo it
5. Over HTTP send the key as `Authorization: Bearer`, never in the URL, and on 429 wait for the Retry-After reset

### 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, Graphicle or TencentDB Agent Memory?

Graphicle scores 70.1 (BB) on agent readiness against TencentDB Agent Memory's 56 (C), and leads in 5 of 7 scored categories. TencentDB Agent Memory leads on maintenance & community.

### Do Graphicle and TencentDB Agent Memory need an API key?

Graphicle takes an API key or an OAuth sign-in. TencentDB Agent Memory needs an API key.

### Can an agent call Graphicle and TencentDB Agent Memory without installing anything?

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

### Are Graphicle and TencentDB Agent Memory open source?

Yes. Graphicle is open source (Apache-2.0). TencentDB Agent Memory is open source (MIT).


## For agents

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

## Other comparisons with Graphicle or TencentDB Agent Memory

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

---

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