La Marzocco MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAMARZOCCO_SERIAL | No | Use this machine serial instead of the one chosen during `lamarzocco-mcp setup`. | |
| LAMARZOCCO_MCP_ALLOW_WRITE | No | Set to "1" to register the optional write tools (set_power, set_steam, set_steam_target_level, set_coffee_target_temperature, set_pre_extraction_mode, set_pre_extraction_times, set_smart_standby). Off by default. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Access to La Marzocco home espresso machines through La Marzocco's cloud (unofficial, not affiliated with La Marzocco). Times are ISO 8601 in the user's local time. Shot durations (extractionSeconds) are pump time as measured by the machine, which is usually a few seconds shorter than a scale's timer. This server is read-only: it cannot turn the machine on or off or change any setting.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_machinesA | List the La Marzocco machines on the account: model, name, serial number, online state. |
| get_machine_statusA | Current machine status: on or standby, coffee and steam boiler state and targets, pre-brewing, and back flush. From the dashboard in La Marzocco's app. |
| get_machine_settingsC | Machine settings: firmware versions, wifi signal, plumb-in, auto-update. |
| get_statisticsC | The statistics widgets selected in La Marzocco's app, e.g. the last coffees and the total coffee and flush counters. |
| get_firmware_statusB | Firmware update status (whether the machine is up to date or updating). |
| get_scheduleC | Smart standby, wake-up/sleep schedules and early start settings. |
| get_coffee_and_flush_counterB | Total number of coffees and flushes the machine has made. |
| get_last_coffeesA | The machine's most recent shots, newest first (La Marzocco keeps the latest 15). Each shot has its end time, extractionSeconds, dose mode, target temperature and whether La Marzocco considers it valid. extractionSeconds is pump time measured by the machine, not a scale timer, so it is usually a few seconds shorter than a scale shows. |
| get_coffee_and_flush_trendA | Coffees and flushes per day for the last N days, in the user's local timezone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target distinct aspects of a machine, but get_statistics overlaps materially with get_coffee_and_flush_counter, get_last_coffees, and get_coffee_and_flush_trend by potentially returning the same counters or recent shots. get_firmware_status also overlaps somewhat with get_machine_settings, which includes firmware versions. Descriptions help, but an agent could still choose the wrong tool for a simple counter or recent-shot request.
All tool names consistently use snake_case with a clear get_ or list_ verb prefix followed by a specific resource. The convention is predictable throughout the set.
Nine tools is well-scoped for a machine-monitoring server. Each tool maps to a specific dashboard area or data view without excessive granularity.
The read-only monitoring surface is broad: machines, status, settings, firmware, schedules, counters, recent shots, and trends are all covered. Missing control actions such as changing schedules or firmware updates are noticeable, but may be intentionally outside the API's scope.