Gaggiuino MCP Server
The Gaggiuino MCP Server is a lightweight server that provides real-time access to Gaggiuino espresso machine data. With it, you can:
Retrieve the current machine status, including temperature and pressure
Access the latest espresso shot ID
Fetch detailed data for specific shots by ID, enabling in-depth analysis of shot performance and parameters
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Gaggiuino MCP Server analyze my latest espresso shot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gaggiuino-mcp
Gaggiuino MCP Server This is a lightweight Model Context Protocol (MCP) server built for Gaggiuino, the open-source espresso machine controller for the Gaggia Classic. It is designed to integrate easily AI clients that want to display or analyze data from the Gaggiuino system in real time.
This is an article I wrote about this project https://medium.com/@a.klement.w/dialing-in-espresso-using-mcp-server-0207819fe93a
Allows connected clients to:
Retrieve the current machine status
Access the latest shot ID
Fetch shot data for a specified id
Related MCP server: meticulous-mcp
Features
📊 Real-time access to shot telemetry
🌐 Designed for local network access
How to use
Using Claude Desktop
{
"mcpServers": {
"gaggiuino": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/gaggiuino-mcp",
"run",
"gaggiuino.py"
]
}
}
}Installing via Smithery
To install Gaggiuino Espresso Machine Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @AndrewKlement/gaggiuino-mcp --client claudeAvailable Toolsets
Toolset | Description |
| Get latest espresso shot id |
| Get espresso shot data for an id. Args: id: Shot id |
| Get espresso machine status |
Example
User:
analyze the latest espresso shot data
Claude:
I'll retrieve and analyze the latest espresso shot data for you. Let me first check the status of your espresso machine and then get the latest shot information.
getStatus
Now I'll get the ID of the latest espresso shot:
getLatestShotId
Let me retrieve the data for shot #188:
getShotData
Based on the data retrieved, I'll now analyze your latest espresso shot (ID #188). Here's my analysis:
Machine Status and Shot Overview Your machine is currently idle at 57.2°C with -0.1 bar pressure. The shot analyzed was taken on April 19, 2025 (based on the timestamp), with a total duration of 26.5 seconds (265 datapoints at 0.1s intervals).
Profile Information You used the "Leva 9 LR v0.5" profile, which is a multi-phase profile with declining pressure targeting 40g of output. The profile has
A flow-control preinfusion at 7 ml/s
Step-down to 3.5 ml/s flow
Pre-extraction at 1.5 ml/s flow with 3 bar pressure restriction
Pressure ramp to 9 bar over 2 seconds
A series of gradually declining pressure steps (8.8→6.0 bar)
Shot Analysis Preinfusion and Extraction Phases
Preinfusion (0-5s): Started with a high flow rate (6-7 ml/s) with minimal pressure (0.3-0.6 bar), allowing the puck to saturate.
First Pressure Rise (5-10s): Pressure gradually built to ~2.5 bar while flow decreased to ~1.5 ml/s.
Pressure Profile Phase (10-15s): Pressure held around 3 bar with flow reduced to ~0.8 ml/s.
Pressure Ramp (15-20s): Pressure increased from 3 to 8.9 bar over ~5 seconds following the programmed profile.
Declining Pressure Phase (20-26.5s): Pressure gradually declined from ~8.5 to 6.4 bar following the profile steps.
Key Measurements
Final Yield: 38g (based on final shot weight)
Brew Ratio: Unable to determine (coffee dose not provided)
Temperature Stability: Excellent - maintained at 92.8-94.1°C throughout extraction
First Drops: Appeared around 11-12 seconds (~75% into preinfusion)
Peak Flow Rate: 7.2 ml/s (at the beginning)
Peak Pressure: 8.9 bar (at ~20 seconds)
Extraction Dynamics
Flow Rate: Started high (7 ml/s), stepped down to 3.5 ml/s then 1.5 ml/s during preinfusion as programmed, then stabilized at ~2.8 ml/s during extraction.
Water Delivery: Total water pumped was 87.7 ml, with 38g in the cup, suggesting significant water retention in the puck.
Pressure Profile: The pressure curve shows excellent progression from preinfusion through extraction, with a smooth transition to declining pressure.
Performance Assessment This appears to be a technically well-executed shot with good adherence to the programmed profile:
Temperature Control: Excellent stability around 93-94°C
Pressure Curve: Follows the programmed profile with smooth transitions
Extraction Flow: Consistent during main extraction phase
Weight Output: Achieved 38g (close to the 40g target)
Would you like me to provide more specific recommendations about any aspect of this shot, or is there a particular parameter you'd like me to analyze in more detail?
Available Tools
3 toolsgetLatestShotIdB
Get latest espresso shot id.
Inputs: no named parameters.
getShotDataC
Get espresso shot data for an id.
Args:
id: Shot id
Inputs: id (required).
getStatusB
Get espresso machine status.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: getLatestShotId retrieves the most recent shot identifier, getShotData fetches detailed data for a specific shot ID, and getStatus provides machine status information. There is no overlap or ambiguity between these functions.
All three tools follow a consistent verb_noun pattern with camelCase naming (getLatestShotId, getShotData, getStatus). The naming is predictable and uniform throughout the set.
With only 3 tools, the set feels thin for an espresso machine control server. There are obvious gaps in functionality, such as tools to start/stop shots, adjust settings, or manage profiles, which limits the server's utility for comprehensive machine interaction.
The tool surface is severely incomplete for an espresso machine domain. It only provides read-only operations (getLatestShotId, getShotData, getStatus) with no ability to control the machine (e.g., start_shot, set_temperature), update configurations, or manage other critical aspects like brewing profiles or maintenance.
Maintenance
Related MCP Connectors
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Real-time planetary signal engine and Model Context Protocol (MCP) server for autonomous AI agents.
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Related MCP Servers
- AlicenseBqualityBmaintenanceLocal-first MCP server that connects AI agents to your Withings body, sleep, activity and heart data.23168 npm6MIT
- AlicenseAqualityDmaintenanceMCP server for controlling Meticulous espresso machines via Claude and other AI clients.22105 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server for Gaggiuino-modified espresso machines, enabling monitoring, shot analysis, and profile management.411 npm1MIT
- AlicenseNot gradedqualityBmaintenanceA remote MCP server for integrating Gaggiuino espresso machines with AI tools. It enables checking machine status, analyzing shot data, managing profiles, and receiving dial-in guidance.1MIT