AnyList API and MCP server Let your AI agent write your AnyList grocery list.

ToolWhat it doesAccess

• list_lists Shopping lists of your account with the number of items left on each. read

  Returns every list in the account, with its name and how many items are not crossed off. Use list as the list parameter of the other tools. Shared lists appear like your own.

  MCP callanylist_read → list_lists

  REST endpointGET https://cotlet.dev/api/v1/anylist/lists

  Parameters

  No parameters.

  Example response

  {
    "lists": [
      {
        "list": "Groceries",
        "items_left": 7,
        "items_crossed_off": 3
      },
      {
        "list": "Hardware store",
        "items_left": 2,
        "items_crossed_off": 0
      }
    ]
  }

• get_list Items of one list with category, quantity, note and whether each is crossed off. read

  Returns the items in the order AnyList shows them, grouped by category. Each item has its name, quantity and note when you set them, and crossed_off. Crossed off items come back only when you ask for them.

  MCP callanylist_read → get_list

  REST endpointGET https://cotlet.dev/api/v1/anylist/list

  Parameters

  Parameters: get_list

  Name	Type	Description
  list string required	string	Name of the list, as list_lists returns it.
  include_crossed_off boolean	boolean	Also return crossed off items. Default: false.

  Example input

  {
    "list": "list"
  }

  Example response

  {
    "list": "Groceries",
    "items": [
      {
        "name": "Oat milk",
        "category": "Dairy",
        "quantity": "2",
        "note": null,
        "crossed_off": false
      },
      {
        "name": "Avocados",
        "category": "Produce",
        "quantity": "2",
        "note": "ripe",
        "crossed_off": false
      }
    ]
  }

• list_favorites Favorite items of one list, the master list of what you buy often. read

  Returns the favorites saved on that list, with the category and the details AnyList keeps for them. An item that is already on the list is marked on_list.

  MCP callanylist_read → list_favorites

  REST endpointGET https://cotlet.dev/api/v1/anylist/favorites

  Parameters

  Parameters: list_favorites

  Name	Type	Description
  list string required	string	Name of the list. Favorites are kept separately for each list.

  Example input

  {
    "list": "list"
  }

  Example response

  {
    "list": "Groceries",
    "favorites": [
      {
        "name": "Bananas",
        "category": "Produce",
        "on_list": false
      },
      {
        "name": "Oat milk",
        "category": "Dairy",
        "on_list": true
      }
    ]
  }

• add_list_item Add an item to a list, with optional quantity, note and category. writeasks first

  Adds one item to the list. A shared list shows the change to everyone you share it with. An item that is already on the list is not added twice. By default you confirm each call; you can switch that off for this tool.

  MCP callanylist_write → add_list_item

  REST endpointPOST https://cotlet.dev/api/v1/anylist/list-items

  Parameters

  Parameters: add_list_item

  Name	Type	Description
  list string required	string	Name of the list.
  name string required	string	Item name, for example "Oat milk".
  quantity string	string	Quantity, for example "2".
  note string	string	Note shown under the item.
  category string	string	Category as it exists on the list. Without it AnyList picks one.

  Example input

  {
    "list": "Groceries",
    "name": "Oat milk",
    "quantity": "2",
    "category": "Dairy"
  }

  Example response

  {
    "list": "Groceries",
    "item": {
      "name": "Oat milk",
      "category": "Dairy",
      "quantity": "2",
      "crossed_off": false
    },
    "added": true
  }

• cross_off_item Cross off an item on a list, or put it back. writeasks first

  Changes one item. People sharing the list see it cross off. An unknown item name fails and the list stays as it was. By default you confirm each call; you can switch that off for this tool.

  MCP callanylist_write → cross_off_item

  REST endpointPOST https://cotlet.dev/api/v1/anylist/off-item/cross

  Parameters

  Parameters: cross_off_item

  Name	Type	Description
  list string required	string	Name of the list.
  name string required	string	Item name as get_list returns it.
  crossed_off boolean	boolean	true crosses it off, false puts it back. Default: true.

  Example input

  {
    "list": "list",
    "name": "Jane Doe"
  }

  Example response

  {
    "list": "Groceries",
    "item": "Avocados",
    "crossed_off": true
  }

• delete_crossed_off_items Delete all crossed off items of a list. writeasks first

  Removes every crossed off item and leaves the rest. Deleted items cannot be brought back through Cotlet. The call returns the names it removed. By default you confirm each call; you can switch that off for this tool.

  MCP callanylist_write → delete_crossed_off_items

  REST endpointDELETE https://cotlet.dev/api/v1/anylist/crossed-off-items

  Parameters

  Parameters: delete_crossed_off_items

  Name	Type	Description
  list string required	string	Name of the list.

  Example input

  {
    "list": "list"
  }

  Example response

  {
    "list": "Groceries",
    "deleted": [
      "Avocados",
      "Dish soap",
      "Bananas"
    ],
    "items_left": 4
  }

ToolWhat it doesAccess

• list_recipes Recipes in your account, optionally from one recipe collection or matching a search. read

  Returns recipe names with their collections, so you can pick one and call get_recipe. Recipes shared by your household appear with your own.

  MCP callanylist_read → list_recipes

  REST endpointGET https://cotlet.dev/api/v1/anylist/recipes

  Parameters

  Parameters: list_recipes

  Name	Type	Description
  collection string	string	Name of a recipe collection.
  query string	string	Words to match in the recipe name.

  Example response

  {
    "recipes": [
      {
        "recipe": "Lemon pasta",
        "collections": [
          "Weeknight"
        ]
      },
      {
        "recipe": "Sheet pan chicken",
        "collections": [
          "Weeknight",
          "Family"
        ]
      }
    ]
  }

• get_recipe One recipe with ingredients, preparation steps and servings. read

  Returns the ingredients with their quantities, the preparation steps in order and the servings. It reads the recipe as saved and does not scale it.

  MCP callanylist_read → get_recipe

  REST endpointGET https://cotlet.dev/api/v1/anylist/recipe

  Parameters

  Parameters: get_recipe

  Name	Type	Description
  recipe string required	string	Name of the recipe, as list_recipes returns it.

  Example input

  {
    "recipe": "recipe"
  }

  Example response

  {
    "recipe": "Lemon pasta",
    "servings": 4,
    "ingredients": [
      "400 g spaghetti",
      "2 lemons",
      "60 g parmesan"
    ],
    "steps": [
      "Boil the pasta.",
      "Toss with lemon zest, juice and parmesan."
    ]
  }

• create_recipe Save a new recipe from text: name, ingredients and steps. writeasks first

  Adds the recipe the way AnyList does when you paste text into it. Household members who share your recipes see it. Photos are not uploaded. By default you confirm each call; you can switch that off for this tool.

  MCP callanylist_write → create_recipe

  REST endpointPOST https://cotlet.dev/api/v1/anylist/recipes

  Parameters

  Parameters: create_recipe

  Name	Type	Description
  name string required	string	Recipe name.
  ingredients array required	array	One string per ingredient, with quantity.
  steps array	array	One string per preparation step.
  servings integer	integer	Number of servings.
  collection string	string	Name of a recipe collection to put it in.

  Example input

  {
    "name": "Jane Doe",
    "ingredients": "ingredients"
  }

  Example response

  {
    "recipe": "Lemon pasta",
    "servings": 4,
    "ingredients_saved": 3,
    "steps_saved": 2,
    "collection": "Weeknight"
  }

ToolWhat it doesAccess

• get_meal_plan Entries of the meal planning calendar between two dates. read

  Returns the recipes and notes on each day of the range, in calendar order. Days with nothing planned are left out.

  MCP callanylist_read → get_meal_plan

  REST endpointGET https://cotlet.dev/api/v1/anylist/meal-plan

  Parameters

  Parameters: get_meal_plan

  Name	Type	Description
  from date required	date	First day, YYYY-MM-DD.
  to date required	date	Last day, YYYY-MM-DD.

  Example input

  {
    "from": "2026-10-01",
    "to": "2026-10-01"
  }

  Example response

  {
    "entries": [
      {
        "date": "2026-10-26",
        "type": "recipe",
        "title": "Lemon pasta"
      },
      {
        "date": "2026-10-27",
        "type": "note",
        "title": "Leftovers"
      }
    ]
  }

• add_recipe_to_meal_plan Put a recipe on a day of the meal planning calendar. writeasks first

  Adds the recipe to that day. The meal plan is shared with your household, so they see the entry. It does not add ingredients to a list; use add_meal_plan_ingredients_to_list for that. By default you confirm each call; you can switch that off for this tool.

  MCP callanylist_write → add_recipe_to_meal_plan

  REST endpointPOST https://cotlet.dev/api/v1/anylist/recipe-to-meal-plans

  Parameters

  Parameters: add_recipe_to_meal_plan

  Name	Type	Description
  recipe string required	string	Name of the recipe.
  date date required	date	Day, YYYY-MM-DD.

  Example input

  {
    "recipe": "recipe",
    "date": "2026-10-01"
  }

  Example response

  {
    "date": "2026-10-28",
    "recipe": "Sheet pan chicken",
    "added": true
  }

• add_meal_plan_ingredients_to_list Add the ingredients of the planned recipes in a date range to a list. writeasks first

  Adds every ingredient of the recipes planned from the first to the last day, the way "Add All Ingredients to List" does in the Meal Plan tab. AnyList combines similar ingredients into one item. It returns the items added. By default you confirm each call; you can switch that off for this tool.

  MCP callanylist_write → add_meal_plan_ingredients_to_list

  REST endpointPOST https://cotlet.dev/api/v1/anylist/meal-plan-ingredients-to-lists

  Parameters

  Parameters: add_meal_plan_ingredients_to_list

  Name	Type	Description
  list string required	string	Name of the list that receives the ingredients.
  from date required	date	First day, YYYY-MM-DD.
  to date required	date	Last day, YYYY-MM-DD.

  Example input

  {
    "list": "list",
    "from": "2026-10-01",
    "to": "2026-10-01"
  }

  Example response

  {
    "list": "Groceries",
    "from": "2026-10-26",
    "to": "2026-11-01",
    "recipes": 5,
    "items_added": 23
  }