Cookidoo MCP
Connect an AI assistant to Cookidoo for recipe creation and translation, guided Thermomix settings, customer-recipe images, shopping lists, and weekly meal planning.
This is an unofficial community project. It is not affiliated with Vorwerk, Thermomix, or Cookidoo.
Run it
Python 3.12 or newer is required. Provide your Cookidoo login through the
COOKIDOO_EMAIL and COOKIDOO_PASSWORD environment variables, then run:
uvx cookidoo-mcp
To keep credentials out of an MCP client's JSON configuration, point the
launcher at a local file containing COOKIDOO_EMAIL and
COOKIDOO_PASSWORD. You may also set COOKIDOO_COUNTRY and
COOKIDOO_LANGUAGE; they default to Cookidoo International English
(ro + en):
uvx cookidoo-mcp --env-file /absolute/path/to/.env
The command starts a local MCP server over stdio. Recipe, image, and calendar
mutations support a dry_run preview so an assistant can show the exact planned
change before applying it. See the
guided setup wizard, the
friendly setup guide, or
the source repository for
client configuration, security notes, examples, and the complete tool
reference.
Metadata
Release files for cookidoo-mcp 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cookidoo_mcp-1.2.0.tar.gz | 42.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cookidoo_mcp-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.6 kB
Release files / cookidoo_mcp-1.2.0.tar.gz
| Download URL | cookidoo_mcp-1.2.0.tar.gz |
|---|---|
| Size | 42.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ceae895bf538888cdb775337cbcecc7dc29d3f4a802e81eae4d5ae1de1998189
|
|
BLAKE2b-256 checksum How to use checksums |
81eda51fdf3f02b08214ffc3ff7bcccc17b728ca428a369708c28c3be24d25c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2026.
Transparency logRelease files / cookidoo_mcp-1.2.0-py3-none-any.whl
| Download URL | cookidoo_mcp-1.2.0-py3-none-any.whl |
|---|---|
| Size | 28.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5cbd2535e75b47c30b43dc30d3efb118423b1437c1803cab2a3fdbe4c074a288
|
|
BLAKE2b-256 checksum How to use checksums |
b1bf1a142ab7c3c08c043ae624f3a8b3bb686acd242ab42858800fdb139f5fe0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2026.
Transparency logSecurity for cookidoo-mcp 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cookidoo_mcp-1.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.