cortex-local-memory
Related Servers
Alternatives to cortex-local-memory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenancePersistent memory for AI agents as a single Go binary: hybrid recall, self-building knowledge graph, and a live TUI dashboard. Zero infra, offline-first — works with Claude Code, Cursor, Codex, OpenCode, and any MCP client.5491MIT
- AlicenseAqualityBmaintenanceLocal-first memory layer for AI coding agents — Markdown as source of truth, MCP server + CLI, human-reviewed capture, team knowledge via git PRs613779 npm6Apache 2.0
- AlicenseBqualityCmaintenancePersistent memory engine for AI coding agents. Single Go binary, zero runtime dependencies, MCP-native. Stores, searches, and deduplicates memories across sessions using embedded SQLite with hybrid FTS + semantic search, memory decay, relation graph, and token-budget context assembly.1023MIT
- AlicenseAqualityFmaintenanceLocal-first MCP memory server that gives AI coding agents long-term memory via SQLite and sqlite-vec, with optional LLM-powered layering. No gateway or API key required.7109 npm4MIT
- AlicenseAqualityCmaintenanceA local MCP server that lets coding agents persist decisions, conventions and gotchas across sessions and recall them with ranked search. Each memory is anchored to the files it describes, so recall flags it as stale when that code changes, and secrets are redacted before anything is stored.52MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that gives AI coding agents a persistent code map and memory, so they can retrieve relevant code with exact file:line pointers and rationale instead of re-reading files. It also lets agents save findings for future sessions and flags notes as stale when referenced files change.48 PyPI5Apache 2.0
TDQS
Scored across 14 tools
Search tools are cleanly separated by target: cortex_search (knowledge base), cortex_memory_search (memories), and cortex_code_search (code with file:line). The main overlap is among the three overview/status tools — cortex_health, cortex_stats, and cortex_map all return counts and status information — and between cortex_context and cortex_project_context, though the descriptions differentiate them well enough.
All 14 tools share a uniform cortex_ prefix and snake_case, with a coherent cortex_memory_* family covering write/batch/write/delete/delete_batch/search. The only deviation is that top-level tools use single nouns (map, plan, stats, health) while the memory family uses resource_verb, but the grouping is predictable rather than chaotic.
14 tools sit comfortably in the well-scoped range and each one serves a distinct retrieval, memory-management, or introspection function. No tool looks redundant filler; the memory batch/delete_batch variants correspond to real bulk needs.
Memory operations cover write, batch write, search, delete, and batch delete, and the knowledge base side covers search, code search, planning, context assembly, and introspection. However, there is no memory update/edit or direct get-by-id/list operation, so retrieving a specific known memory relies entirely on search, and no tool apparently indexes documents, implying ingestion happens elsewhere.