dev-diary-mcp
Related Servers
Alternatives to dev-diary-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceTurns any folder of Markdown files into a searchable, structured knowledge base for Claude Code, enabling persistent memory across sessions via tools like list, read, write, edit, search, and summarize.MIT
- AlicenseNot gradedqualityBmaintenanceTurns a folder of Markdown notes into an agent-native knowledge base, providing long-term memory with provenance, token-budgeted retrieval, and safe write-back with versioning.MIT
- AlicenseNot gradedqualityDmaintenanceGives AI agents full-text search over any Markdown/MDX documentation folder.9 npmMIT
- AlicenseNot gradedqualityCmaintenancePersistent shared memory for AI coding agents that turns a folder of markdown files into searchable memory across sessions, repos, and machines.10 npmFunctional Source , Version 1.1, MIT Future
- AlicenseNot gradedqualityAmaintenanceTransforms a folder of Markdown files into a structured, version-controlled knowledge base with semantic search and safe AI editing via draft branches.MIT
- AlicenseNot gradedqualityCmaintenanceEnables semantic search over personal Markdown journal entries by indexing them with Ollama embeddings into a SQLite vector store and exposing retrieval through a Streamable HTTP MCP endpoint at /mcp.MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action on the diary: append (log_work), replace (edit_entry), remove (delete_entry), full-text lookup (search_diary), date-scoped listing (daily_summary), and aggregate metrics (stats). The retrieval tools could superficially overlap, but their descriptions clearly separate full-text search, per-date listing, and aggregate statistics.
Four tools follow a clean verb_noun snake_case pattern (log_work, edit_entry, delete_entry, search_diary). The two read-only views, daily_summary and stats, drop the verb and are bare noun phrases, a minor but noticeable deviation in an otherwise consistent set.
Six tools is well-scoped for a personal diary server: one write, one update, one delete, and three read/query shapes. Nothing appears redundant and no obvious capability is missing from the surface.
Full lifecycle coverage exists: create, edit, delete, search, date view, and stats, so agents won't hit dead ends for core workflows. Minor gaps remain, such as tag-based filtering/listing, retrieving entries across a custom date range, or fetching a single entry directly without search.