dreamd
Related Servers
Alternatives to dreamd
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents persistent, file-based memory stored as plain markdown files in a local git repository, enabling agents to remember, recall, and build on information across sessions.4 npm1MIT
- AlicenseAqualityBmaintenanceA fully local MCP server that gives AI agents persistent, semantic long-term memory without any cloud dependencies.11388 npm2MIT
- AlicenseAqualityBmaintenanceA 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.161MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.5 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server providing persistent, layered memory (episodic, semantic, procedural, resource) for AI agents, with search, versioning, and session management via a single SQLite file.74 npm3MIT
TDQS
Scored across 2 tools
append_node (write an episodic event) and search_nodes (read events + lessons) are clearly opposite operations with explicit 'use when' triggers that prevent misselection. The shared abstract noun 'node' and the embedded HTTP-API references (recall?explain=1) add minor noise but do not create real overlap.
Both tools follow the same verb_noun snake_case pattern and share the '_node' resource suffix, making the pair predictable and symmetric (write vs. read).
Two tools is on the thin side for a memory server; the write and recall pair covers the core loop but leaves nothing for management operations. Borderline rather than inappropriate.
The essential write-then-recall lifecycle is present, and lessons are intentionally produced by the dream cycle rather than a tool. However there is no way to delete/forget a bad memory, update or correct an event, or fetch a specific node by id, which are notable gaps for a memory domain.