structured-memory-mcp
Related Servers
Alternatives to structured-memory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to store decisions, patterns, and knowledge once and retrieve relevant context automatically across sessions, surviving context limits, restarts, and compaction.17 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to persistently store and retrieve decisions, patterns, and knowledge across sessions, with workspace organization and semantic search so context survives restarts and compaction.17 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, search, and retrieve durable knowledge through a relationship graph, with on-demand context assembly, history, and cascaded stale marking when underlying facts change.GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to persistently store, retrieve, and organize decisions, patterns, and knowledge across sessions, so context survives restarts and compaction.17 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to persistently store and retrieve decisions, patterns, and knowledge across sessions, surviving context limits, restarts, and compaction.17 npmMIT
- AlicenseAqualityCmaintenanceProvides an external context buffer so a local model can maintain session memory across long tasks and search and page through large documents without loading them whole into its limited context window.151MIT
TDQS
Scored across 20 tools
Most tools target distinct resources and actions, but read_memory and search_memory overlap heavily (both hybrid search the trail), and write_memory vs write_wiki could be confused about where durable information belongs. The detailed descriptions help, but the boundaries are not perfectly crisp.
All tool names use snake_case with a consistent verb_noun pattern (load_wiki, retire_constraint, write_memory, list_constraints, track_thread, etc.). The convention is predictable throughout with no mixed styles.
20 tools is heavy for a single MCP server and sits in the borderline range. While each tool covers a distinct facet (memory, wiki, constraints, threads, friction, records, session state), the surface could likely be consolidated to reduce selection overhead.
The server covers core lifecycle operations across its subdomains: memory read/write/search/walk, wiki load/write/list, constraints list/set/retire, threads list/track/touch, friction log/list/triage, and records log/list. Missing hard delete/update for memories, records, and wiki pages may be intentional by design, but still leaves minor gaps.