cookidoo-mcp

Purpose: Accessing and automating Cookidoo/Thermomix recipes, shopping lists, and meal plans through AI agents and the Model Context Protocol.

Inferred · not functionally tested

Audience: developers

Inferred · not functionally tested

Functions: agents, data_extraction

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: Apache-2.0 · platforms: CLI · deployment: cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

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

In the Frameworks & runtimes space, cookidoo-mcp takes a focused approach. Inferred · not functionally tested: It focuses on accessing and automating Cookidoo/Thermomix recipes, shopping lists, and meal plans through AI agents and the Model Context Protocol. Inferred · not functionally tested: It is built as an open-source project for developers. Basis unknown · not verified: cookidoo-mcp is open source under the Apache-2.0 license. Basis unknown · not verified: It runs on the command line and API, and it can be self-hosted.

Vitalie Miron builds and maintains cookidoo-mcp, and it first shipped in 2026. Development happens publicly on GitHub with 24 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include MCP Server, Recipe Retrieval, and Shopping List Generation. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

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