Skip to main content
Glama
dev-diary-mcp

dev-diary-mcp

by rogeriolaa

Related Servers

Alternatives to dev-diary-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Persistent shared memory for AI coding agents that turns a folder of markdown files into searchable memory across sessions, repos, and machines.
      10 npm
      Functional Source , Version 1.1, MIT Future
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data