AnyList MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_recipesA | List all saved recipes from the AnyList account. Returns name, rating, cook time, prep time, and servings for each recipe. Use the optional search parameter to filter by name. |
| get_recipe_detailsA | Get full details of a specific recipe including ingredients and preparation steps. Look up by name or ID. |
| get_meal_planA | Get meal plan events for a date range. Defaults to the current week (Mon-Sun). Use a 6-week lookback (e.g. start_date 6 weeks ago) to understand recent eating patterns when recommending new meals. |
| add_meal_plan_eventC | Schedule a recipe or titled event on a specific day in the meal plan calendar. |
| get_listsA | List all shopping lists in the AnyList account. |
| get_list_itemsB | Get all items on a specific shopping list. |
| add_item_to_listA | Add a freeform item to a shopping list. Checks for duplicates before adding. |
| add_ingredient_to_listA | Add a specific ingredient from a recipe to a shopping list. Matches existing items or recent items by name for proper AnyList categorization. |
| add_recipe_ingredients_to_listA | Add all ingredients from a single recipe to a shopping list. Defaults to the "Groceries" list. Checks for duplicates: skips items already on the list, unchecks previously checked-off items. |
| add_ingredients_to_listA | Add ingredients from multiple recipes to a shopping list at once. Defaults to the "Groceries" list. Handles duplicates across recipes: each ingredient is only added once. |
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 10 tools
There is significant overlap between tools like add_ingredients_to_list, add_ingredient_to_list, add_recipe_ingredients_to_list, and add_item_to_list, which all add items to shopping lists with subtle distinctions that could confuse an agent. However, the descriptions provide some clarity on their specific use cases, such as handling multiple recipes versus single recipes versus freeform items.
All tool names follow a consistent verb_noun pattern with snake_case, such as add_ingredients_to_list, get_list_items, and get_meal_plan. This predictability makes it easy for an agent to understand and navigate the tool set without confusion.
With 10 tools, the server is well-scoped for managing shopping lists, recipes, and meal plans. Each tool serves a distinct purpose within this domain, and the count is neither too sparse nor overwhelming, fitting typical server ranges of 3-15 tools.
The tool set covers core operations for shopping lists (add, get), recipes (get details, list), and meal plans (add events, get plan), with minor gaps such as missing update or delete functions for items, lists, or recipes. Agents can likely work around these omissions, but they represent a slight limitation in lifecycle coverage.