CPersona
OfficialRelated Servers
Alternatives to CPersona
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenancePersistent AI memory server with 3-layer hybrid search (vector + FTS5 + keyword), confidence scoring via Reciprocal Rank Fusion, episodic/profile memory, and 16 tools. Zero LLM dependency. Works standalone with Claude Desktop and Claude Code. MIT licensed.3Business Source 1.1
- AlicenseNot gradedqualityDmaintenancePersistent memory MCP server for Claude Code. Store, search, and retrieve memories across sessions using hybrid vector + keyword search powered by SQLite, FTS5, and sqlite-vec.27 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP memory server built on SQLite + FTS5, providing cross-session long-term memory for Claude Code.-

Loreofficial
AlicenseBqualityAmaintenanceCross-agent memory server: hybrid (vector + full-text + knowledge-graph) recall, per-user private/shared visibility, write-side secret/PII redaction, and as-of-date bi-temporal fact queries. Auto-injection hooks for Claude Code / Cursor / Codex; self-hostable on PostgreSQL or SQLite.4657 PyPI8MIT- AlicenseAqualityCmaintenanceLocal-first memory for Claude Code and any MCP client: hybrid vector + keyword search and a bi-temporal knowledge graph in one SQLite file. Local embeddings, no API key, $0/token.51168 npm2PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityAmaintenanceCross-client AI memory hub for AI agents. Lets Claude Code, Cursor, Windsurf, and 20+ other clients share one physical SQLite memory database. Features bi-temporal time axes, source attribution, Q-Value usage-based ranking, and FTS5 full-text search with SQLite triggers.1Apache 2.0
TDQS
Scored across 34 tools
Most tools target clearly distinct operations, and the very detailed descriptions carefully separate recall/reconstruct/recall_with_context and check_health/get_session_findings/deep_check. However, the recall variants and the two overlapping health-reporting seams mean an agent must read carefully to choose correctly.
All tool names use consistent snake_case, overwhelmingly in a verb_noun pattern (store, recall, get_profile, delete_memory, pause_persistence, set_recall_precision). There is no camelCase or mixed-convention drift, and the few bare verbs (recall, store) remain readable and conventional.
34 tools is well above the 3–15 sweet spot and past the 25-tool threshold, making the surface heavy for an agent to navigate even if most tools have distinct purposes. Several capabilities are split into read/write/status trios (pause/resume/persistence_status, set/get_recall_precision), which adds further bulk.
The surface covers memory CRUD, episodes, profiles, declared associations, recall/reconstruction, health checks, persistence control, precision tuning, import/export/merge, migration, and update checks — a broad lifecycle. Minor gaps remain, such as no standalone delete_profile, but core workflows are well covered.