Mealie MCP Server

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

38/38 tools missing one or more hints — mealie_about (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mealie_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mealie_search_recipes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +35 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — mealie_api_download deletes at line 2331 (target.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — mealie_api_download (line 2331: target.unlink(missing_ok=True))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

35/38 tool handlers declare input schemas (92%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 5/38 tool handlers wrap calls in try/catch (13%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

mealie_api_download: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.