Skip to main content
Glama
talvola

bar-assistant-mcp

by talvola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to bar-assistant-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-paprika

      bojanrajkovic
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Paprika recipe manager enabling search, CRUD operations, grocery lists, meal planning, and menus via natural language, with semantic search and background sync.
      14 npm
      2
      MIT

    • receitas-mcp-server

      laizaguedes
      F
      license
      A
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage a recipe catalog, including listing, searching, adding, removing, and suggesting recipes, with optional Trello or local JSON storage.
      5
      -

    • Barkeeper

      NickM-27
      F
      license
      A
      quality
      C
      maintenance
      A simple MCP server for tracking a home bar's inventory and cocktail recipes, with tools to manage shelf items and recipe details.
      7
      -
    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

    B3.2/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the detailed descriptions explicitly guide users between lookalikes (e.g. bar_audit_ingredients vs bar_list_ingredients, search vs list). The main overlap is bar_search_cocktails vs bar_list_cocktails and bar_search_ingredients vs bar_list_ingredients, where the boundary (name search vs filtered browse) is real but somewhat blurry.

    Naming Consistency4/5

    Nearly all tools follow a consistent bar_ + snake_case pattern (bar_get_/list_/create_/update_/delete_/set_/add_). A handful deviate from the verb_noun convention (bar_makeable_cocktails, bar_favorite_cocktails, bar_uses_for_bottle, bar_alternatives_for_slot), but these remain readable and uniformly prefixed.

    Tool Count3/5

    41 tools is heavy and pushes into territory where an agent must scan a large surface. The domain (cocktails, ingredients, flavor matching, shelf, constraints) is genuinely broad and justifies many of these, but some tools stretch the scope beyond what a single server comfortably handles.

    Completeness4/5

    Strong CRUD coverage for cocktails and ingredients plus flavor profiling, slot constraints, shelf, and matching workflows. Minor gaps: shopping list supports add/get but no remove, and collections/tags/glasses/methods are list-only, though these may be read-only reference data.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources