brewfather-mcp
Related Servers
Alternatives to brewfather-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceThis remote server provides a comprehensive interface for the Brewfather platform. It enables users to manage recipes, track ingredients, and update batch statuses and hydrometer readings through an MCP client.MIT
- AlicenseAqualityCmaintenanceRead-only MCP server exposing Brewfather brewing data—batches, recipes, fermentation readings, and inventory—as tools for natural language queries.91MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read, create, and update brewing recipes, inspect inventory, batches, and Tilt/iSpindel fermentation readings, and move batches between statuses via a self-hosted remote connector on Cloudflare Workers.MIT
- AlicenseAqualityBmaintenanceEnables LLM clients to read batches, recipes, fermentation readings, and inventory, and to perform routine writes such as updating batch status, logging measurements, and adjusting stock.13MIT
- FlicenseNot gradedqualityDmaintenanceWraps 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.-
- AlicenseAqualityDmaintenanceEnables AI coding agents to browse, read, write, delete, and search Cooklang recipes through the CookCLI HTTP API as MCP tools.7MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.