Plan to Eat MCP

Purpose: Automating access to Plan to Eat recipes, meal plans, freezer inventory, and shopping lists from agents or the terminal.

Inferred · not functionally tested

Audience: developers and users automating Plan to Eat workflows

Inferred · not functionally tested

Functions: agents, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: API, CLI · deployment: cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the CLI tools & terminal space, Plan to Eat MCP takes a focused approach. Inferred · not functionally tested: It focuses on automating access to Plan to Eat recipes, meal plans, freezer inventory, and shopping lists from agents or the terminal. Inferred · not functionally tested: Plan to Eat MCP is an open-source project aimed at developers and users automating Plan to Eat workflows. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: Plan to Eat MCP is available on the command line and API, and it can be self-hosted.

It is developed by Alex Zwingli. Inferred · not functionally tested: Among its 6 catalogued features are recipe management, meal planning, and freezer tracking. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.