cc-memory
Related Servers
Alternatives to cc-memory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEmbedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.753 PyPI43Apache 2.0
- AlicenseAqualityBmaintenanceEnables coding agents to store, search, update, and delete durable facts, preferences, decisions, and plans in a shared local SQLite database, along with per-namespace profile get/set and stats. Uses offline lexical FTS5 search so multiple agents working on the same project can share one memory store.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to persist and retrieve project-scoped memories across sessions using local SQLite FTS5 keyword search.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.8 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to keep durable long-term memory on the user's own machine, writing sessions and messages into a local SQLite database and retrieving them via keyword, exact, or optional semantic search with surrounding context. Runs entirely offline over stdio, so no cloud service or API key is required to give an agent recall across sessions.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to persistently save, search, retrieve, update, link, and forget project-scoped memories through MCP tools, using local SQLite FTS5 keyword search without cloud access or telemetry.4MIT
TDQS
Scored across 8 tools
Search, recent, and topics all retrieve memories but differ by mode (full-text, recency, topic summaries), and descriptions clarify compact vs full details. Some overlap between memory_recent and memory_search could cause occasional misselection.
All tools use snake_case with consistent domain prefixes (memory_, progress_), and no mixed conventions. The pattern is predictable and readable.
8 tools is well-scoped for a memory plus progress management server, with each tool serving a distinct purpose. No tools feel redundant or missing at the count level.
Covers create (add with upsert), read (search, get details, recent, topics, stats), and progress read/regenerate, but lacks an explicit delete or archive operation. Agents can work around this via supersede behavior in memory_add.