Skip to main content
Glama
cacack

mcp-server-brewfather

by cacack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-server-brewfather

No user-submitted related servers found.

    Related Servers

    • Brewfather MCP Server

      flattery89
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server exposing Brewfather brewing data—batches, recipes, fermentation readings, and inventory—as tools for natural language queries.
      9
      MIT
    • Tulip MCP Server by tulip

      Tulip MCP Serverofficial

      tulip
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to interact with the Tulip manufacturing platform, providing access to tables, records, machines, stations, interfaces, users, and other manufacturing operations through the Tulip API.
      30
      13 npm
      6
      Apache 2.0

    • mcp-logistica

      noelaliaga
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to query a warehouse management system for orders, stock, stalled orders, and audit logs, and to make narrowly scoped writes by changing order status with a required reason or appending notes, with all writes recorded in a full audit trail.
      MIT

    • Brewman MCP Server

      PaddyWalsh81
      F
      license
      Not graded
      quality
      D
      maintenance
      Wraps the Brewman Web (V7) API to read and write Brewman data (orders, outlets, stock, config) via tools, with the API token stored securely as an environment variable.
      -
    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/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: recipes (find/get/create/update), batches (find/get/update/readings/brewtracker), and inventory (list/set/create/update). The only potentially confusable pair, set_inventory vs update_inventory_item, is explicitly disambiguated in the descriptions (stock vs details).

    Naming Consistency4/5

    Names are uniformly snake_case verb_noun (get_batch, create_recipe, update_inventory_item), which is predictable and readable. Minor deviation: enumeration-style operations mix 'find' (find_recipes, find_batches) and 'list' (list_inventory), and single-item reads use 'get', which is a slight inconsistency but semantically motivated.

    Tool Count5/5

    13 tools is well within the ideal range and each one earns its place, mapping cleanly onto the three domains (recipes, batches, inventory) without redundancy. No thin single-tool areas and no bloat.

    Completeness4/5

    Read/update coverage is strong across recipes, batches, and inventory, including specialized reads (readings, brewtracker) and careful split of inventory stock vs details. Gaps: no delete operations for recipes or inventory items, and no batch creation or log/event writing, though these are minor for a primarily read-and-adjust workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources