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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/june4432/thermo-control-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server