MCP Govee
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOVEE_API_KEY | Yes | Your Govee API key (obtained from Govee Home app) | |
| GOVEE_API_BACKEND | No | Backend to use: v1, v2, or lan | v1 |
| GOVEE_LAN_ENABLED | No | Set to 'true' to enable LAN backend (requires GOVEE_API_BACKEND=lan or using tool parameter) | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List all Govee devices on your account |
| get_device_stateA | Get the current state of a Govee device (power, brightness, color) |
| set_powerB | Turn a Govee device on or off |
| set_brightnessA | Set the brightness of a Govee device (0-100) |
| set_colorB | Set the color of a Govee device using RGB values |
| set_color_temperatureB | Set the color temperature of a Govee device in Kelvin (2000-9000) |
| list_scenesA | List built-in dynamic light scenes available for a device (v2 backend only) |
| list_diy_scenesB | List user-created DIY scenes for a device (v2 backend only) |
| activate_sceneB | Activate a built-in or DIY scene by name (v2 backend only) |
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
Each tool has a clearly distinct purpose. The scene-related tools differentiate built-in from DIY scenes, and all control tools target different attributes (power, brightness, color, color temperature). No significant overlap.
All tools follow a consistent verb_noun pattern in snake_case (e.g., set_brightness, list_devices). The naming is predictable and clear, with no mixing of conventions.
9 tools is well-scoped for a smart light controller. Each tool earns its place covering device discovery, state retrieval, power control, color adjustments, and scene management. Not too many or too few.
The tool set covers core operations: listing devices, getting state, setting power, brightness, color (RGB and temperature), and scenes. Missing features like device renaming or setting effects are minor and not essential for typical use.