CP Memory
Related Servers
Alternatives to CP Memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.1 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes a local SQLite-backed long-term memory to AI agents as MCP tools, letting them add conversations and documents, record dated facts with provenance, search and assemble context, and edit, inspect, or forget what was stored. It runs with your own embedding and LLM keys, so memories stay readable, exportable, and portable as plain markdown.MIT
- AlicenseNot gradedqualityBmaintenancePersistent long-term memory for MCP clients. Store and recall semantic facts, episodic events, and task state with vector-based relevance search. Write what matters, retrieve what's needed — memory that persists across sessions and agents, backed by a local SQLite store with optional embeddings for meaning-based lookup. Simple file-based storage, no external services required.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.10 npmMIT
- AlicenseBqualityBmaintenanceLocal long-term memory service for AI agents via MCP, using SQLite with tools for memory CRUD, semantic search, time-based facts, and graph capabilities.2711 npm1MIT
TDQS
Scored across 40 tools
Several tools have unclear boundaries: memory_add vs memory_update vs memory_personal_add overlap, and memory_correct, memory_review_apply, and memory_personal_resolve all support similar marking actions. The review cluster (memory_personal_review, memory_review_digest, memory_review_inbox) and retrieval cluster (memory_search, memory_recall, memory_restore_context) also create confusion.
Most tools follow a memory_<noun>_<verb> pattern, but there are notable exceptions like memory_add, memory_list, memory_recall, memory_restore_context, memory_review_digest, and memory_review_inbox. The naming is readable and consistently prefixed with memory_, but the mixed verb/noun order and noun-only names prevent a higher score.
At 40 tools, this server is overbuilt for a coherent tool set. Many tools could be consolidated, especially the review, correction, and inspection clusters, which inflate the count without adding clear distinct value.
The core memory lifecycle is well covered with add, update, remove, search, inspect, aliases, links, conflicts, maintenance, and governance tools. Minor gaps exist in subdomains such as workflows, decisions, aliases, and links, where add/list/save exists but dedicated remove/update operations are missing or indirect.