Skip to main content
Glama
chrisscott

Swizzler MCP

by chrisscott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Swizzler MCP

No user-submitted related servers found.

    Related Servers

    • Bar Assistant MCP Server

      zhdenny
      A
      license
      A
      quality
      D
      maintenance
      Enables intelligent cocktail discovery and recipe retrieval from Bar Assistant instances with natural language search, similarity matching, batch processing, and ingredient analysis capabilities.
      3
      3
      MIT

    • Cocktail

      Yusuke-Shibata23
      F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -

    • Shaky

      akquisio-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives your AI a live picture of your home bar's spirits, liqueurs, juices, garnishes, equipment and glassware, so it can suggest cocktails you can actually make right now, propose substitutes, help use up open bottles before they turn, and keep a shopping list. Runs locally alongside a web UI where you and the AI read and write the same inventory, with fill levels, expiry dates and every change logged.
      MIT

    • Cocktails MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching for cocktail recipes by name, ingredient, or randomly, and retrieving full cocktail details including ingredients, measurements, and instructions via TheCocktailDB API.
      435 npm
      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.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (ingredient matching, search, history, queue, collections). The main overlap is snapshot_status vs diagnose_sync, both about library freshness/sync, though the descriptions differentiate reporting status from explaining causes.

    Naming Consistency4/5

    All names use snake_case consistently, which is good. However, the verb/noun patterns vary: some are verb_noun (search_recipes, get_recipe, list_collections), others are plain nouns (recipe_history, snapshot_status) or question phrasing (what_can_i_make, whats_next).

    Tool Count5/5

    Eight tools is well-scoped for a cocktail library assistant, each covering a distinct user intent without redundancy or bloat.

    Completeness4/5

    Read-side coverage is strong: discovery, search, detail, history, queue, collections, and sync troubleshooting. The surface appears read-only with no write operations (e.g. rating or adding recipes), a minor gap if mutation is in scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources