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
      58 npm
      5
      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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair: find/get/update for batches, get for readings, find/get/update for recipes, list/set for inventory. The find-versus-get distinction (search by name/status vs. read one by id) is spelled out in descriptions, leaving little room for misselection.

    Naming Consistency4/5

    All tools use consistent snake_case verb_noun form and the read/update pattern repeats cleanly across batches and recipes. Minor deviation: retrieval uses three different verbs (find_*, get_*, list_*) and mutation uses both update_* and set_*, which is defensible but slightly inconsistent.

    Tool Count5/5

    Nine tools is well within a comfortable range and the surface is tightly scoped to the domain's three entities (batches, recipes, inventory). Every tool earns its place with no redundancy.

    Completeness3/5

    Coverage is read- and update-heavy: batches and recipes can be searched, read, and edited, but there are no create or delete operations for batches, recipes, or inventory items. This is a notable lifecycle gap for an agent trying to start new batches or add recipes, though the operational update path is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources