cortex-memory
Related Servers
Alternatives to cortex-memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.29MIT
- AlicenseNot gradedqualityBmaintenanceProvides coding agents with governed semantic memory and code-graph context via MCP, enabling code-linked recall, blast-radius impact analysis, and lifecycle-aware memory management.3Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.4MIT
- AlicenseAqualityAmaintenanceMCP-native, local-first memory for coding agents that turns real sessions into reusable decisions, gotchas, and domain knowledge.176MIT
- FlicenseNot gradedqualityBmaintenancePersistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain a private, local-first persistent memory by automatically saving, searching, and retrieving structured project memories through MCP, with hybrid keyword and embedding search, feedback-driven ranking, and no cloud dependency.1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct memory operation: error-loop checking, scratchpad updates, hybrid retrieval, graph inspection, consolidation, and event recording. There is minimal overlap between querying, inspecting, and recording.
All tools share the cortex_ prefix and follow a consistent snake_case verb_noun pattern. The naming clearly communicates action and target.
Six tools is a well-scoped set for a memory server, covering retrieval, recording, updates, inspection, and maintenance without redundancy.
Core memory workflows are covered, but there is no explicit delete/forget or scratchpad reset operation, which could be a minor gap depending on expected memory lifecycle management.