Skip to content
MCP server

Parsley MCP by usefulapi

Read Parsley menu items, nutrition, allergens, ingredients and events; record event…

Install
Runs
Remotely
Version
1.19.0
Listing updated
4 days ago

About Parsley MCP by usefulapi

Parsley MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.

Read Parsley menu items, nutrition, allergens, ingredients and events; record event sales and waste.

Install

Run in a terminal

claude mcp add --transport http parsley https://parsley.usefulapi.io/mcp

Add to Settings → Connectors → Add custom connector

https://parsley.usefulapi.io/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "parsley": {
      "url": "https://parsley.usefulapi.io/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "parsley": {
      "type": "http",
      "url": "https://parsley.usefulapi.io/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "parsley": {
      "serverUrl": "https://parsley.usefulapi.io/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "parsley": {
      "type": "http",
      "url": "https://parsley.usefulapi.io/mcp"
    }
  }
}

Tools this server provides (15)

Read directly from the server.

parsley_list_menu_items
List the recipes, sub-recipes and ingredients in the Parsley account that can be used on events: id, name, item number, price, tags, active flag, chef and last-modified time. Use the ids with parsley_get_menu_item for nutrition, allergens and ingredients, and on events. The API returns the whole list at once; search/limit/offset slice it here. GET /menu_items.
parsley_get_menu_item
One menu item in full: names, description, price, cost, shelf life, serving size, nutrition facts (nutrients), the allergen flags and allergen text, dietary characteristics (meat, pork, corn, poultry) and the ingredient list. The photo link is returned without its access token. GET /menu_items/{id}.
parsley_list_menus
List the menus (menu plans) in the account: id, name and last-modified time. Use the id with parsley_get_menu or when creating an event. GET /menus.
parsley_get_menu
One menu with its sections and the menu items in each section, and its serving stations. GET /menus/{id}.
parsley_list_ingredients
List the ingredients that can be used in recipes: id, parent id, name, label name, item number, supported units, and whether a recipe uses it. The API returns the whole list at once; search/limit/offset slice it here. GET /ingredients.
parsley_get_ingredient
One ingredient in full: unit conversions, supported units, tags, the supply options (supplier, SKU, pack size, cost) used for costing and the preparations with yield. Parsley limits this call to 1 request every 3 seconds, so fetch ingredients one at a time. GET /ingredients/{id}.
parsley_list_events
List events (a workday, shift, service or catering event) that fall in a date window: id, name, type (standard, cafe-hot-bar, sale, forecast), date, start and end time, menu id. A bare date means the whole day in the account timezone. GET /events.
parsley_get_event
One event with its metadata and all line items (menu item, amount, unit, station, section). GET /events/{id}.
parsley_list_serving_stations
List the serving stations (id, name) that menu items and event line items can be assigned to. GET /tags/serving_stations.
parsley_list_chef_tags
List the chef tags (id, name) that recipes are attributed to. Only meaningful for accounts with Chef IDs enabled. GET /tags/chefs.
parsley_list_chef_users
List the chef users of the account: id, email, join date, active flag, permission level and the chef tag they are tied to. Only meaningful for accounts with Chef IDs enabled. GET /users/chefs.
parsley_create_event
WRITE: create an event (a workday, shift, service or catering event) in Parsley with its menu items. This changes the account's production plan and is NOT idempotent: calling it twice creates two events. Returns the new event id. Use parsley_list_events first to avoid duplicates. POST /events.
parsley_update_event_covers
WRITE: set the forecast and/or actual number of covers (guests served) on an event. Only the fields you pass change. actual_covers works only on cafe/hot bar events. Setting the same values again has no further effect. PATCH /events/{id}.
parsley_record_event_sales
WRITE: push sold quantities per menu item to a cafe/hot bar event, which feeds Parsley's cost and usage reports. Other event types are refused by Parsley, as is a menu item with no made quantity on the event. Sending the same quantities again overwrites rather than adds. PUT /events/{id}/sales.
parsley_record_waste_leftover
WRITE: push waste and/or leftover quantities per menu item to a cafe/hot bar event. If no sold quantity exists, Parsley derives it as made minus waste minus leftover. Parsley refuses amounts above what was made minus sold. Sending the same quantities again overwrites rather than adds. PUT /events/{id}/waste_leftover.

Parsley MCP by usefulapi FAQ

How do I add Parsley MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http parsley https://parsley.usefulapi.io/mcp