lamarzocco-mcp
Unofficial. This project is not affiliated with, endorsed by, or supported by La Marzocco.
An MCP server that lets Claude and other MCP clients read the status, settings and shot data of La Marzocco home espresso machines, and optionally change a few settings. It runs locally over stdio and is built on pylamarzocco.
Ask things like "what was my last shot?", "is the machine on?" or, with write tools enabled, "turn on the machine".
Supported machines
Developed and tested on a Linea Micra. Other models supported by pylamarzocco should work; see docs/capabilities.md for what has been verified per model.
Requirements
- uv (it installs Python 3.13 for you if needed)
- A La Marzocco account that uses a regular email/password login (not Google or Apple sign-in)
- The machine connected to wifi and set up in La Marzocco's app
Setup
Store your La Marzocco login in the system keyring (macOS Keychain, Windows Credential Locker, or the Secret Service on Linux). Nothing is written to disk:
uvx lamarzocco-mcp setup
It signs in, lists your machines and saves the one to use. Run it again to change account, or
uvx lamarzocco-mcp setup --delete to remove everything. On macOS, the first time the server reads
the keychain you may be asked to allow it; choose "Always Allow".
Use with Claude
The server runs over stdio: your MCP client starts it when needed, so there is nothing to keep running.
Claude Code:
claude mcp add --scope user lamarzocco -- uvx lamarzocco-mcp
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS),
then restart Claude Desktop:
{
"mcpServers": {
"lamarzocco": {
"command": "uvx",
"args": ["lamarzocco-mcp"]
}
}
}
If Claude Desktop cannot find uvx, use its full path (which uvx, e.g.
/opt/homebrew/bin/uvx).
Tools
Read-only by default. Each tool wraps one method of pylamarzocco's LaMarzoccoCloudClient.
| Tool | Returns |
|---|---|
list_machines |
Machines on the account |
get_machine_status |
On/standby, boilers, pre-brewing, back flush |
get_machine_settings |
Firmware, wifi signal, plumb-in, auto-update |
get_statistics |
Statistics widgets from the app |
get_firmware_status |
Firmware update status |
get_schedule |
Smart standby and wake-up/sleep schedules |
get_coffee_and_flush_counter |
Total coffees and flushes |
get_last_coffees |
Latest 15 shots: time, extraction (pump) seconds, dose, temperature |
get_coffee_and_flush_trend |
Coffees and flushes per day, up to 30 days |
Responses are La Marzocco's raw JSON with three changes: timestamps become ISO 8601 in local time, the Bluetooth token and wifi name are redacted, and image/tutorial URLs are dropped.
Shot times (extractionSeconds) are pump time measured by the machine, usually a few seconds
shorter than a scale's timer.
Optional write tools
Off by default. With LAMARZOCCO_MCP_ALLOW_WRITE=1 in the server's environment, seven more tools
are registered:
| Tool | Changes |
|---|---|
set_power |
On (brewing mode) or standby |
set_steam |
Steam boiler on/off |
set_steam_target_level |
Steam level 1–3 (level-based machines such as the Linea Micra) |
set_coffee_target_temperature |
Coffee boiler target, °C |
set_pre_extraction_mode |
Pre-brewing on/off (or pre-infusion, where the machine has it) |
set_pre_extraction_times |
Pre-brewing seconds in and out |
set_smart_standby |
Automatic standby after N minutes |
Each request is checked against the limits the machine reports before it is sent, and the setting is read back afterwards. Back flush, plumb-in, firmware updates and schedules are not exposed.
To enable them in Claude Desktop, add an env block to the server entry:
"lamarzocco": {
"command": "uvx",
"args": ["lamarzocco-mcp"],
"env": { "LAMARZOCCO_MCP_ALLOW_WRITE": "1" }
}
In Claude Code: claude mcp add --scope user -e LAMARZOCCO_MCP_ALLOW_WRITE=1 lamarzocco -- uvx lamarzocco-mcp.
Configuration
| Variable | Effect |
|---|---|
LAMARZOCCO_MCP_ALLOW_WRITE=1 |
Registers the write tools |
LAMARZOCCO_SERIAL |
Use this machine instead of the one chosen in setup |
With several machines on the account, tools also take an optional serial_number.
Security
- Your login and installation key are stored only in the system keyring.
- The server runs only locally over stdio; there is no network listener.
- Read-only unless you enable write tools.
- The server uses La Marzocco's undocumented cloud API through pylamarzocco, the same API their app uses. It can stop working if La Marzocco changes it.
Contributing
Have a different La Marzocco model? Mapping what it returns takes about ten minutes; see CONTRIBUTING.md.
Credits
- pylamarzocco by Josef Zweck (MIT)
- The Home Assistant La Marzocco integration
License
MIT
Metadata
Release files for lamarzocco-mcp 0.1.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 | Actions |
|---|---|---|---|---|
| lamarzocco_mcp-0.1.0.tar.gz | 16.5 kB | With provenance | Details for lamarzocco_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lamarzocco_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lamarzocco_mcp-0.1.0-py3-none-any.whl |
Total release size: 36.6 kB
Release files / lamarzocco_mcp-0.1.0.tar.gz
| Download URL | lamarzocco_mcp-0.1.0.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66350d60a3cc807bb29a6ad062b91eb95d9cd096e37f769bb1c8dc139a0e3c01
|
|
BLAKE2b-256 checksum How to use checksums |
3af7ed856c38991558e5bd7ae64d83209edd3cd6e015ddde22c9de4f3e83466c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logRelease files / lamarzocco_mcp-0.1.0-py3-none-any.whl
| Download URL | lamarzocco_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 20.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6311b4e94d4b564163ddef5f1bf9aaae7381bb5c5927560bc30032d36fb9753d
|
|
BLAKE2b-256 checksum How to use checksums |
1d036e31edd3925ddc7ba4f0cc543e742e4198d373348b1c12abb3b229724ad7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logSecurity for lamarzocco-mcp 0.1.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
Both files in this release have been uploaded with provenance metadata.
Attestation for lamarzocco_mcp-0.1.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 Nov 15, 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.