Swizzler MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWIZZLER_LIBRARY_PATH | No | Path to the Swizzler library snapshot. By default it reads ~/Library/Mobile Documents/iCloud~com~getswizzler~app/Documents/Library.swizzle. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snapshot_statusA | Report how current the local Swizzler library snapshot is, and where it came from. Use this when the user asks whether their recipes are up to date, or when a recipe they expect seems to be missing. |
| diagnose_syncA | Explain why the Swizzler library is missing or not updating, by checking iCloud Drive on this Mac and the state of the snapshot file. Use when recipes are missing or stale. |
| search_recipesA | Search the user's own cocktail library by name, ingredient, spirit, or collection. Returns one line per match. Omit every filter to list the whole library. |
| get_recipeA | Full details for one recipe in the user's library, by name or id. |
| whats_nextB | Recipes the user has flagged "Next Round" in Swizzler — the queue of drinks they mean to make next. Use for "what's up next", "what am I making next", "what's in my queue". |
| list_collectionsA | List the user's recipe collections and how many recipes each holds. |
| what_can_i_makeB | Given the bottles and ingredients the user has on hand, find recipes they can make. Set allowMissing above 0 to include near-misses and see what is missing. |
| recipe_historyB | What the user has actually made and how they rated it, from their "Made It" history. Use for questions like what they drink most or which recipes they rated highest. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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).
Eight tools is well-scoped for a cocktail library assistant, each covering a distinct user intent without redundancy or bloat.
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.