Bar Assistant MCP Server
Related Servers
Alternatives to Bar Assistant MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables natural language search for cocktail recipes and ingredient information through TheCocktailDB API. Supports searching by cocktail name, ingredient, category, or alcohol content to discover recipes and recommendations.5-
- FlicenseAqualityDmaintenanceEnables management of your home bar inventory and cocktail discovery through Bar Assistant. View shelf ingredients, find cocktails you can make, and add or remove items from your bar collection.6-
- AlicenseAqualityAmaintenanceProvides read-only access to a personal cocktail library stored in a synced on-device snapshot, letting AI assistants search recipes by name, ingredient, spirit, or collection, retrieve full drink specs, list collections, determine which drinks can be made from the bottles on hand, and review what has been made and how it was rated. Every result reports the snapshot's age so stale data is flagged rather than silently trusted.820 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching for cocktail recipes by name, ingredient, or randomly, and retrieving full cocktail details including ingredients, measurements, and instructions via TheCocktailDB API.2 npmMIT
- AlicenseCqualityDmaintenanceEnables searching for cocktail recipes by name or ingredients using the API Ninjas Cocktail API, supporting partial matches and ingredient-based filtering.1MIT
- AlicenseBqualityDmaintenanceMCP server for Bar Assistant that enables searching cocktails, managing ingredients, shelves, shopping lists, and collections via natural language.41MIT
TDQS
Scored across 3 tools
The three tools have distinct primary purposes: get_ingredient_info focuses on ingredient details and substitutions, get_recipe retrieves specific cocktail recipes, and smart_search_cocktails searches for cocktails based on various criteria. However, there is some functional overlap between get_recipe and smart_search_cocktails, as both can return complete recipes, which could cause minor confusion for an agent deciding which to use for recipe retrieval.
The tool names follow a consistent verb_noun pattern (get_ingredient_info, get_recipe, smart_search_cocktails), which is clear and predictable. The only minor deviation is that smart_search_cocktails uses an adjective (smart) before the verb_noun structure, but this is still readable and maintains overall consistency.
With three tools, this server is well-scoped for a bar assistant domain, covering key areas like ingredient information, recipe retrieval, and cocktail search. Each tool serves a distinct and valuable function, and the count is neither too sparse nor overwhelming, making it easy for an agent to navigate and use effectively.
The toolset covers core functionalities for a bar assistant, such as ingredient lookup, recipe fetching, and cocktail search. However, there are notable gaps in the lifecycle coverage; for example, there are no tools for creating, updating, or managing cocktails or ingredients (e.g., add_recipe, update_ingredient), which limits the server's utility for more interactive or creative tasks beyond retrieval and search.