Dev Context Memory MCP
Related Servers
Alternatives to Dev Context Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server that turns a .context/ folder of markdown files into a searchable knowledge layer for AI coding agents.9 npm2MIT
- AlicenseAqualityCmaintenanceA local-first MCP server that provides a shared Markdown-based memory for AI coding agents, enabling cross-agent context persistence via tools like memory_search and memory_capture.101MIT
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3760 npm6MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that gives AI coding assistants persistent, project-scoped memory across sessions, storing facts and decisions in a SQLite database under .aimem/ and exposing tools for searching, storing, and conflict-resolving memories.30 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.6 npmMIT
- AlicenseNot gradedqualityAmaintenanceA local-first MCP server that gives AI coding agents durable project memory, dependency graphs, and impact analysis to answer team knowledge and cross-file change questions before editing.28 npm1-
TDQS
Scored across 7 tools
Each tool has a clear, distinct purpose: append tools for adding structured entries, retrieval tools for accessing memory, and write for overwriting sections. No ambiguity between tools.
All tools follow a consistent verb_noun pattern in snake_case (e.g., append_api_contract, list_memory_sections), making the set predictable and easy to navigate.
With 7 tools covering creation, retrieval, and overwriting of memory sections, the set is well-scoped. Each tool earns its place without being redundant or excessive.
The tools support appending and reading memory, but lack explicit delete or edit functionality for sections or individual entries. write_memory can overwrite but not delete, and no tool allows partial updates.