Mealie MCP Server

Overview Schema Source Related Servers Discussions Admin

mealie_api_get

Retrieve recipe, meal planning, and shopping list data from your self-hosted Mealie instance via authenticated GET requests, validated against live OpenAPI and security tags.

Instructions

Generic authenticated GET validated against live OpenAPI and security tags.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "mealie_api_get"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`params`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 5, 2026

TDQS

C2.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the tool is authenticated and validates requests against the live OpenAPI and security tags, which is useful behavioral context. However, it does not describe response handling, error behavior, or whether redirects are followed. With no annotations, more detail would be expected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler words. It conveys the core message efficiently, though it is under-specified in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, one might expect more context about what paths are valid and how params are used. There is no output schema, and the description is too sparse for an agent to reliably construct requests. The presence of many sibling tools makes the role of this generic tool less obvious.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain the 'path' or 'params' parameters beyond what the schema already shows. Since schema description coverage is 0%, the description was expected to compensate by clarifying the format (e.g., is path a URL fragment? are params query parameters?), but it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a generic authenticated GET request, using a specific verb and resource (Mealie API). It distinguishes itself from specific sibling tools like mealie_get_recipe by being generic, and from other API tools like mealie_api_request by explicitly stating 'GET'. However, it does not elaborate on the intended use case beyond being a catch-all.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus sibling alternatives like mealie_api_request or mealie_api_operation_request. The description only states what the tool is, not when to choose it over other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server