mcp-structured-memory
Related Servers
Alternatives to mcp-structured-memory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceProvides centralized knowledge management for projects, allowing users to store, search, and maintain project-specific knowledge that persists across sessions.2714 npm1-
- AlicenseNot gradedqualityBmaintenanceGives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.11Apache 2.0
- AlicenseBqualityCmaintenanceProvides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.1661 npm2MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with structured access to project conventions, technology stacks, and architectural patterns to ensure consistency across development teams.-
- AlicenseNot gradedqualityAmaintenanceEnables agents to maintain persistent project context locally, with source-backed memory and structured handoffs for seamless handover between interchangeable agents.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents like Claude and Codex to store, search, and exchange project knowledge such as architectural decisions and work packets, with tenant isolation for security.-
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific operations on structured memory documents. For example, add_to_list, move_list_item, and update_list_item are all focused on list management but handle different actions (adding, moving, updating), while get_full_memory, get_memory_summary, and get_section provide different levels of retrieval detail. There is no ambiguity in tool selection.
All tools follow a consistent verb_noun naming pattern (e.g., create_memory, list_memories, update_section). The verbs are clear and descriptive, and there are no deviations in style or convention throughout the set, making it predictable and easy to understand.
With 10 tools, the count is well-scoped for managing structured memory documents. Each tool serves a specific function in the lifecycle (create, retrieve, update, search, list), and none feel redundant or unnecessary, fitting the domain appropriately without being overwhelming.
The tool set provides complete coverage for the structured memory domain, including creation (create_memory), listing (list_memories), retrieval at various levels (get_full_memory, get_memory_summary, get_section), updating (update_section, update_list_item), list management (add_to_list, move_list_item), and search (search_within_memory). There are no obvious gaps, and the tools support full CRUD and lifecycle operations.