io.github.Umarjaum/repo-memory-mcp
Related Servers
Alternatives to io.github.Umarjaum/repo-memory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local-first persistent memory layer for coding assistants, enabling cross-project user preferences, per-project durable and working memory, session archives, and reflective recommendations through MCP tools.43 npmMIT
- AlicenseBqualityCmaintenanceProvides local, explicitly scoped memory for coding agents via MCP, storing durable project knowledge in a per-repository SQLite database with tools to record, search, and retrieve context.5MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides long-term local memory for AI coding agents via MCP, enabling persistent recall of preferences and project facts across chat sessions.1MIT
- AlicenseBqualityAmaintenanceProvides local-first durable memory and session continuity for AI coding agents over MCP, enabling context across restarts without cloud services or telemetry.21MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct roles, but the remember_correction / remember_rule / remember_decision trio and list_project_rules overlapping list_memories create minor ambiguity. The descriptions explain the differences well enough for an agent to choose correctly.
All tool names follow a consistent snake_case verb_noun pattern: list_, update_, forget_, remember_, recall_, get_, export_, import_. The memory-themed vocabulary is coherent and predictable.
11 tools is well-scoped for a repository memory system: create variants, read/search, update, archive, export/import, and startup context. Each tool earns its place and the set does not feel bloated.
The surface covers create, read, search, update, archive, export, import, and startup context. The main gap is no explicit restore/unarchive operation for archived memories, but this can likely be worked around via update_memory or export data.