Skip to main content
Glama
plane636

brewfather-mcp

by plane636
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to brewfather-mcp

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

    • 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.
      -

    • Tandoor MCP Server

      mc-mario
      A
      license
      B
      quality
      C
      maintenance
      Enables interaction with Tandoor recipe management system to create, manage, and search recipes, as well as create and auto-generate meal plans with automatic ingredient and keyword creation.
      11
      56 npm
      3
      MIT

    • Cookbook Shelf MCP

      jameslupolt
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only listing of the cookbooks on an Eat Your Books shelf and searching those books for recipe references by ingredient, dish, or keyword, returning links, authors, page numbers, ingredients, and categories. Connects to an already signed-in local Chrome session for authentication, exposing the same service as the CLI through two read-only tools.
      2
      MIT
    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.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: connection check, listing, searching, retrieving, previewing/creating, and previewing/updating. The list vs. search tools are differentiated by description (compact vs. filtered) and the preview/apply pairs are unambiguous.

    Naming Consistency4/5

    Most tools follow the pattern 'brewfather_' + verb + '_' + noun (e.g., list_recipes, get_recipe, apply_recipe_create). However, 'brewfather_connection_status' deviates as a noun phrase rather than an action, creating a minor inconsistency.

    Tool Count5/5

    With 8 tools, the server is well-scoped for recipe management. It covers connection validation, read operations (list/search/get), and a two-phase create/update workflow, each tool earning its place without bloat.

    Completeness3/5

    The surface covers read (list/search/get) and create/update with preview/apply, but there is no delete operation, leaving a notable gap in the lifecycle. Other potential operations (e.g., duplicate, export) are absent but the core is covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources