context-keeper
Related Servers
Alternatives to context-keeper
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing Claude with persistent, local memory for tracking architectural decisions, dead ends, and project context across conversations.MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code, Cursor, Codex and Claude Desktop to carry project decisions, rules, bugs and dead ends across sessions, writing them to a repo file and bringing the relevant lines back next time, and checks each command or file edit against saved rules before it runs. Works over MCP so teams share the same memory through git.848 npmMIT
- AlicenseCqualityAmaintenanceStores and recalls Claude Code session content as persistent memory, auto-injects relevant prior decisions and lessons at session start, and exposes 33 MCP tools for memory, knowledge-graph navigation, and cognitive profiling — backed by 41 neuroscience papers and 97.8% R@10 on LongMemEval.406 npm276 PyPI75MIT
- AlicenseNot gradedqualityCmaintenancePersistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.266 npm1MIT
- AlicenseAqualityAmaintenancePost-hoc session handoff and project memory for Claude Code: MCP tools list_sessions and handoff turn any session — even crashed or usage-limit-hit ones — into a clean handoff.md another model can continue from, with secrets redacted from every output. Zero dependencies, fully local; also distills a project's entire session history into one cited memory brief.279 PyPI1MIT
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose: creation, retrieval by relevance, structured filtering, overview, snapshot export, update, deprecation, stale pruning, compaction reporting, quality verification, markdown export, constraint reloading, snapshot import, and remote sync. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., record_entry, get_context, export_snapshot). The single verb 'mirror' is common and fits the pattern of operations.
14 tools cover the full scope of context management without bloat. Each tool addresses a specific need (CRUD, maintenance, export/import, sync) and the count is appropriate for the domain.
The tool surface covers the full lifecycle: create, read (multiple modes), update, deprecate, export/import, sync, maintenance (pruning, quality checks), and constraint management. No obvious gaps for the stated purpose of project context management.