Skip to main content
Glama
norrietaylor

io.github.norrietaylor/distillery-mcp

Official
by norrietaylor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to io.github.norrietaylor/distillery-mcp

No user-submitted related servers found.

    Related Servers

    • Rememberizer MCP Server

      skydeckai
      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

    • Rememberizer MCP Server

      skydeckai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic search and retrieval of information from personal and team knowledge repositories including Slack, Gmail, Dropbox, Google Drive, and uploaded files. Allows storing new information for future recall through AI-powered search.
      Apache 2.0
    • Beever Atlas by Beever-AI

      Beever Atlasofficial

      Beever-AI
      A
      license
      A
      quality
      A
      maintenance
      Turns team chat (Slack, Discord, MS Teams, Mattermost) into a living knowledge base - a typed knowledge graph plus auto-generated wiki - exposed to AI agents through a 28-tool MCP server with semantic search, expert finding, and decision tracing.
      28
      444
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessResponsive

    Resources