thermo-control-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_thermal_statusA | Read the Mac's current thermal state: per-sensor die temperatures (CPU/GPU/memory), fan RPM (actual/target/min/max) and mode, power draw in watts, and the fan-control state (manual targets, remaining TTL, last automatic revert). Use this before and after changing fan speeds, or to decide whether pre-cooling is worthwhile. |
| set_fan_speedA | Put the Mac's fans into manual mode at a given speed. Provide either 'rpm' (absolute) or 'percent' (0-100, mapped onto each fan's min-max range). Values are clamped to the hardware's reported safe range. The setting expires after ttl_seconds (default 900, max 7200) and fans return to system control — call again to renew. A root-owned failsafe overrides manual control if any die sensor reaches 102°C. Typical use: raise fans BEFORE starting a heavy build/inference job so the machine stays out of thermal throttling. |
| boost_fansA | Convenience wrapper: run all fans at 100% for a limited time (default 600 s). Good for pre-cooling right before a compile, video export, or LLM inference burst. Reverts automatically. |
| set_fan_autoA | Release manual fan control immediately and hand thermal management back to macOS (thermalmonitord). Use when the heavy workload is done. |
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 4 tools
Each tool has a clearly distinct purpose: boosting fans, reading status, setting auto mode, and setting manual speed. No overlap.
All tool names follow the consistent snake_case pattern with a verb_noun structure: boost_fans, get_thermal_status, set_fan_auto, set_fan_speed.
4 tools are well-scoped for a thermal control server, covering status, manual control, auto release, and a convenience function.
The tool set covers the essential operations for fan control: reading status, setting manual speed, reverting to auto, and a burst mode.