Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Parsley MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Parsley menu items, nutrition, allergens, ingredients and events; record event sales and waste.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http parsley-mcp-by-usefulapi https://parsley.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# parsley_list_menu_items, parsley_get_menu_item, parsley_list_menus and 12 more
Parsley MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 598 servers
usefulapi598 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http parsley-mcp-by-usefulapi https://parsley.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only menu items whose name contains this text (case-insensitive). |
| type | string | no | Only this kind of item. |
| tag | string | no | Only items carrying this tag (exact, case-insensitive). |
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| menu_item_id | integer | yes | Parsley menu item id (from parsley_list_menu_items). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only menus whose name contains this text (case-insensitive). |
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
One menu with its sections and the menu items in each section, and its serving stations. GET /menus/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| menu_id | integer | yes | Parsley menu id (from parsley_list_menus). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only ingredients whose name contains this text (case-insensitive). |
| used_by_recipe | boolean | no | true: only ingredients used by a recipe; false: only unused ones. |
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ingredient_id | integer | yes | Parsley ingredient id (from parsley_list_ingredients). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Window start (inclusive): yyyy-mm-dd or an ISO 8601 date-time. Without a timezone the account timezone applies. |
| end | string | yes | Window end (inclusive): yyyy-mm-dd (to the end of that day) or an ISO 8601 date-time. |
| search | string | no | Only events whose name contains this text (case-insensitive). |
| type | string | no | Only this event type. |
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
One event with its metadata and all line items (menu item, amount, unit, station, section). GET /events/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | integer | yes | Parsley event id (from parsley_list_events). |
List the serving stations (id, name) that menu items and event line items can be assigned to. GET /tags/serving_stations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
List the chef tags (id, name) that recipes are attributed to. Only meaningful for accounts with Chef IDs enabled. GET /tags/chefs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only chef users (matched on email or chef name) whose name contains this text (case-insensitive). |
| limit | integer | no | Results to return, 1-500 (default 100). |
| offset | integer | no | Skip this many results (default 0). Pass the previous reply's next_offset. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Event name, e.g. 'Brunch'. |
| type | string | yes | Event type: standard, cafe-hot-bar, sale or forecast. |
| date | string | yes | The day of the event, yyyy-mm-dd. |
| start_time | string | no | Time of day, HH:mm (24 hour). |
| end_time | string | no | Time of day, HH:mm (24 hour). |
| menu_id | integer | no | Parsley menu id the event uses (from parsley_list_menus). |
| description | string | no | — |
| private | boolean | no | Mark the event private. |
| line_items | array | yes | The menu items and amounts to produce or sell (may be empty). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | integer | yes | Parsley event id. |
| forecast_covers | integer | no | Predicted number of covers. |
| actual_covers | integer | no | Real number of covers (cafe/hot bar events only). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | integer | yes | Parsley event id of a cafe/hot bar event. |
| sales | array | yes | Sold amount per menu item. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | integer | yes | Parsley event id of a cafe/hot bar event. |
| items | array | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Parsley MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.15.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest507936ebeb82bdf2dff5d48c61f04f8662300769fd3dfca47fb317b4b0ae42fd
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| parsley_list_menu_items | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_get_menu_item | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_list_menus | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_get_menu | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_list_ingredients | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_get_ingredient | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| parsley_list_events | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_get_event | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_list_serving_stations | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_list_chef_tags | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_list_chef_users | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| parsley_create_event | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| parsley_update_event_covers | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| parsley_record_event_sales | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| parsley_record_waste_leftover | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest507936ebeb82bdf2
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.15.2.
1.15.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Parsley MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.