A
licenseNot graded
qualityC
maintenanceA persistent, local memory layer for AI coding agents that remembers decisions, bugs, and rules across sessions with three core MCP verbs (recall, remember, search).
Apache 2.0
Mimir
by kamysh
Related Servers
Alternatives to Mimir
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenancePersistent memory and pattern learning for AI coding assistants via MCP.35 npm175MIT
- AlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents2,191 PyPI225Apache 2.0
- FlicenseNot gradedqualityCmaintenancePersistent, self-curating memory for coding agents. It enables local, zero-cost context recall through MCP tools with hybrid retrieval and autonomous consolidation.-
- AlicenseNot gradedqualityBmaintenanceProvides persistent memory for AI coding agents via MCP, allowing them to recall fragility, decisions, and bugs across sessions.198 npm3MIT
- AlicenseNot gradedqualityCmaintenancePersistent cross-session memory for AI coding assistants, automatically capturing and injecting context across sessions via MCP tools.6 npm11AGPL 3.0
This server cannot be deployed
TDQS
C2.9/5.0
Scored across 30 tools
Disambiguation4/5
Tools mostly target distinct resources and actions (beliefs, patterns, edges, evidence, experiences, documents, queries), and descriptions explicitly clarify tricky boundaries such as query_intervention vs query_relevant vs propagate_from. Some overlap remains between query_relevant/query_learning_context and insert_belief/record_experience, but the distinctions are workable.
Naming Consistency4/5
Most tool names follow a snake_case verb_noun pattern (get_belief, insert_pattern, record_defeat, list_beliefs). A few deviate, such as pending_experiences, experience_history, and decay_all, but the overall convention is still readable and consistent enough.
Tool Count2/5
With 30 tools, the server exceeds the 25+ threshold and presents a heavy surface for an agent to navigate, despite the domain being broad. Many tools are granular variants, such as multiple edge recorders, multiple query types, and separate experience inspection calls.
Completeness4/5
Core lifecycle coverage is strong: beliefs can be inserted, fetched, listed, and deleted; patterns can be inserted, listed, and deleted; edges, evidence, documents, experiences/reviews, queries, and maintenance are all represented. Minor gaps include no direct get_pattern, update_belief, or update_pattern, though reviews and decay mechanisms partially cover updates.
Maintenance
ActivityActive
ResponsivenessSlow