# Parsley Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Parsley

Manage menus, events, ingredients and track sales and waste for food service operations.

- Record: https://musedirectory.ai/connector/parsley
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/parsley/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 153ms, checked 2026-10-29T23:41:18Z
- Endpoint: https://parsley.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T23:41:18Z)
- Source: Found in the official MCP Registry (io.usefulapi/parsley) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fparsley

Connect to Parsley food service management software to view and manage menu items, recipes, ingredients, nutrition and allergen data. Create events, record sales and waste for cafe and hot bar operations to track costs and usage.

Example request: "Show me the menu items available for tomorrow's lunch event and record how many portions we sold."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Parsley to help me. It is a free service with an MCP server at https://parsley.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 r
- 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. G
- 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.
- 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 /eve
- 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 

Screening checks:
- MCP handshake: pass (Answered in 153ms)
- Domain against threat feeds (Cloudflare security DNS): pass (parsley.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (15 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)