RAPT.io MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPT_PASSWORD | Yes | Your RAPT password | |
| RAPT_USERNAME | Yes | Your RAPT username (email) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_bonded_devicesA | List all devices bonded to the RAPT account (all device types). |
| get_bonded_deviceA | Get details for a specific bonded device by UUID. |
| get_bonded_device_telemetryC | Get telemetry data for a bonded device. |
| get_fermentation_chambersA | List all fermentation chambers (Gärschränke) in the RAPT account. |
| get_fermentation_chamberA | Get detailed status of a single fermentation chamber including current temperature, target temperature, PID settings, heating/cooling state, run-time statistics, and active profile. |
| set_fermentation_chamber_temperatureA | Set the target temperature for a fermentation chamber. The value is in the unit configured on the device (°C or °F). |
| set_fermentation_chamber_pid_enabledA | Enable or disable PID temperature control for a fermentation chamber. |
| set_fermentation_chamber_pidB | Configure PID parameters (proportional, integral, derivative) for a fermentation chamber's temperature controller. |
| set_fermentation_chamber_heating_enabledB | Enable or disable the heating element of a fermentation chamber. |
| set_fermentation_chamber_cooling_enabledA | Enable or disable the cooling (compressor) of a fermentation chamber. |
| set_fermentation_chamber_fan_enabledA | Enable or disable the fan of a fermentation chamber. |
| set_fermentation_chamber_light_enabledB | Control the light of a fermentation chamber (On, Off, or Auto). |
| set_fermentation_chamber_cooling_hysteresisA | Set the cooling hysteresis (deadband) for a fermentation chamber. Valid range: 0.5–10. |
| set_fermentation_chamber_heating_hysteresisB | Set the heating hysteresis (deadband) for a fermentation chamber. Valid range: 0.1–10. |
| set_fermentation_chamber_compressor_delayA | Set the compressor restart delay in minutes for a fermentation chamber. Valid range: 2–10. |
| set_fermentation_chamber_mode_switch_delayA | Set the heating/cooling mode switch delay in minutes for a fermentation chamber. Valid range: 2–30. |
| get_fermentation_chamber_telemetryA | Get historical telemetry data for a fermentation chamber, including temperature readings, compressor/heating run times, and profile progress. |
| get_hydrometersA | List all hydrometers (RaptPill devices) in the RAPT account. Returns current gravity, temperature, and battery level. |
| get_hydrometerA | Get detailed status of a single RaptPill hydrometer including current gravity (specific gravity), gravity velocity, temperature, and battery level. |
| get_hydrometer_telemetryA | Get historical telemetry data for a RaptPill hydrometer. Returns timestamped gravity, temperature, and battery readings. |
| get_profilesA | List all fermentation profiles saved in the RAPT account. |
| get_profileA | Get details of a specific fermentation profile including all steps and alerts. |
| get_profile_typesA | List all available profile types in the RAPT system. |
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 23 tools
Most tools target distinct resources, but get_bonded_device_telemetry overlaps with resource-specific telemetry endpoints, and get_bonded_device vs get_fermentation_chamber could confuse agents unfamiliar with the domain. Descriptions mostly clarify these boundaries.
All tools follow a consistent snake_case verb_noun pattern: get_* for reads, set_* for writes, and plural forms for list operations. This makes the API highly predictable and easy to navigate.
With 23 tools, the server is slightly heavy, but the count is justified by the breadth of resources (devices, chambers, hydrometers, profiles) and the granular control offered for fermentation chambers. No redundant tools exist.
The server covers monitoring and direct control well, but lacks profile management (create/update/delete) and the ability to assign or start a profile on a chamber. These are notable gaps for a fermentation control system, though core read/control workflows are present.