Skip to main content
Glama
norrietaylor

io.github.norrietaylor/distillery-mcp

Official
by norrietaylor

Related Servers

Alternatives to io.github.norrietaylor/distillery-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic search and retrieval of personal and team knowledge from connected sources like Slack, Gmail, Google Drive, and Dropbox, with the ability to save new information for future recall.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to share a persistent, self-improving memory by ingesting sources like Obsidian vaults, code, transcripts, and session captures, then serving them back through search, classification, synthesis, and token-optimized context briefings. It lets multiple agents read and write the same knowledge base, so each session builds on the last without copy-pasting context.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to capture, classify, synthesize, and retrieve persistent knowledge through MCP and REST APIs, so multiple agents can share memory and improve across sessions. It provides full-text, semantic, and hybrid search with token-optimized context retrieval from sources like Obsidian, code, transcripts, and terminal sessions.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents a shared persistent memory by ingesting Obsidian vaults, code, transcripts, web clips, and session or bug-fix captures, then serving token-optimized context briefings, keyword and semantic search, and cross-source synthesis. Enables multiple agents to read and write the same growing knowledge base so each session builds on the last.
      14 npm
      MIT

    TDQS

    A4.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: store vs store_batch vs ingest_doc handle different ingestion paths, get/update/correct handle modification, list/search/find_similar handle retrieval with different modes, and watch/gh_sync/relations cover external sources and graph operations. The descriptions explicitly call out when to use each over related tools.

    Naming Consistency4/5

    All tools share the 'distillery_' prefix and generally follow a verb-first pattern (store, get, update, list, search, watch, configure, status). Mixed single verbs and compound verb_noun forms (store_batch, ingest_doc, find_similar, resolve_review, gh_sync) are consistent in style; 'relations' is a noun-based command but remains clear. No camelCase or chaotic mixing.

    Tool Count5/5

    17 tools is slightly above the typical 3-15 range but fully justified given the server's broad scope: entry lifecycle, semantic search, duplicate detection, relation graph management, feed monitoring, GitHub sync, and configuration. Each tool addresses a distinct aspect of the domain without redundancy.

    Completeness4/5

    The surface covers create (store, ingest), read (get, list, search), update, and archival (via correct and resolve_review's archive action), plus relation management and feed/sync operations. The only notable gap is the lack of a direct hard-delete tool for entries; archiving effectively serves as a soft delete, but a permanent removal option is missing.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive