marm-memory
Related Servers
Alternatives to marm-memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that provides AI agents with persistent memory, cross-agent sharing, and context management, enabling them to remember conversations, track complex tasks, and evolve skills across tools.2MIT
- AlicenseNot gradedqualityAmaintenanceProvides AI agents with persistent, human-like memory infrastructure via MCP, enabling them to store, search, summarize, and forget episodic, semantic, procedural, and working memories across sessions.715 npmMIT
- AlicenseAqualityBmaintenanceMCP server for persistent, compounding memory that automatically captures corrections and insights across AI sessions, enabling agents to learn and improve over time.5371MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to maintain persistent memory across sessions by capturing conversations, extracting durable knowledge, and injecting relevant context, supporting various MCP-compatible platforms.12MIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent, shared memory for AI agents via MCP, enabling retrieval of relevant memories instead of loading entire context. Allows agents across projects, machines, and tools to share a single auditable, markdown-native brain.3AGPL 3.0
- AlicenseBqualityAmaintenanceMCP server providing persistent memory and context for AI tools, including semantic memory, knowledge graph, and session history to avoid starting from scratch in every conversation.3514MIT
TDQS
Scored across 16 tools
Each tool targets a distinct resource or action: memory distillation, compaction, recall, logging, notebook workflows, summaries, code-graph operations, code lookup/context, and concept-graph operations. Apparent overlaps such as code_lookup vs code_context and smart_recall vs concept_recall are explicitly differentiated in the descriptions.
All names use lowercase snake_case with a marm_ prefix, which is highly consistent. Most follow marm_<domain>_<action>, but some noun-phrase names (marm_code_context, marm_notebook, marm_summary) and bare marm_delete deviate slightly from a strict verb_noun pattern.
16 tools is slightly above the ideal 3-15 range, but the server covers several cohesive subdomains (memory, logs, notebook, code graph, concept graph), so most tools earn their place. It is not excessive for the breadth of functionality.
The surface covers memory creation, compaction, recall, logging, notebook workflows, code-graph indexing/lookup/trace/impact, and concept extraction/recall. Minor gaps remain: no direct update/delete for individual stored memories, and no obvious way to browse memories without a query.