MCP Govee
Enables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.
README
MCP Govee
An MCP server that lets AI assistants control your Govee smart devices. Turn lights on and off, change colors, adjust brightness, activate scenes, and more — all through natural conversation.
Works with Claude Desktop, Claude Code, or any MCP-compatible client.
Use Cases
- Ask your AI to set the mood with natural language — "make it feel cozy" or "I need bright light to focus"
- Coordinate multiple devices with a single request — "turn everything off except the hallway"
- Let your AI manage lighting as part of a larger workflow — "I'm starting a meeting, dim the office lights"
- Use natural language to find and activate scenes without scrolling through the app
- Have your AI check device states and troubleshoot connectivity across backends
Setup
Requires Node.js 18+.
1. Get a Govee API Key
Open the Govee Home app on your phone and go to Settings → About Us → Apply for API Key. You'll receive your key by email.
2. Configure Your MCP Client
Add the server to your MCP client's configuration. There are two ways to do this:
Option A: Run directly from GitHub (no install needed)
{
"mcpServers": {
"govee": {
"command": "npx",
"args": ["-y", "github:danjam/mcp-govee"],
"env": {
"GOVEE_API_KEY": "your-api-key-here"
}
}
}
}
Option B: Clone and run locally
git clone https://github.com/danjam/mcp-govee.git
cd mcp-govee
npm install
Then point your MCP client at the local build:
{
"mcpServers": {
"govee": {
"command": "node",
"args": ["/path/to/mcp-govee/dist/index.js"],
"env": {
"GOVEE_API_KEY": "your-api-key-here"
}
}
}
}
Replace /path/to/mcp-govee with the actual path where you cloned the project.
Backends
The server supports three different ways to communicate with your Govee devices. By default it uses v1, which works for most people out of the box.
| Backend | How it connects | Scenes support | Notes |
|---|---|---|---|
| v1 (default) | Govee cloud API | No | Simplest setup, works with all Govee devices |
| v2 | Govee cloud API (newer) | Yes | Required for scenes; supports the same devices as v1. Much stricter rate limit (see below) |
| lan | Local network (UDP) | No | Fastest, no internet needed, no rate limits, but only works with LAN-capable devices on the same network. You must enable LAN control per device in the Govee Home app (device settings → LAN Control) |
[!WARNING] v2 has a much stricter rate limit. The v1 API allows 100 requests per minute, but the v2 API only allows 10 requests per minute — that's one request every 6 seconds. We recommend leaving v1 as the default and only using v2 when you need scene features.
To change the default backend, add GOVEE_API_BACKEND to your config:
{
"mcpServers": {
"govee": {
"command": "npx",
"args": ["-y", "github:danjam/mcp-govee"],
"env": {
"GOVEE_API_KEY": "your-api-key-here",
"GOVEE_API_BACKEND": "v2"
}
}
}
}
To enable the LAN backend, also set GOVEE_LAN_ENABLED:
"env": {
"GOVEE_API_KEY": "your-api-key-here",
"GOVEE_LAN_ENABLED": "true"
}
You can also override the backend on a per-command basis — every tool accepts an optional backend parameter (v1, v2, or lan). This lets you use v1 as your default while still accessing v2-only features like scenes when you need them. You don't need to set v2 as your default to use scenes — the server will automatically route scene commands to v2.
What You Can Do
List Devices
See all the Govee devices on your account, including their IDs, models, and what commands they support. This is the starting point — you'll need a device's ID and model for all other commands. Only devices added to your Govee Home app will appear, and not all devices support every command.
Tool: list_devices
| Parameter | Type | Required | Description |
|---|---|---|---|
backend |
string | No | Override the default backend (v1, v2, or lan) |
Get Device State
Check the current state of a device: whether it's on or off, the brightness level, and the current color.
Tool: get_device_state
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID (from list devices) |
model |
string | Yes | The device model (from list devices) |
backend |
string | No | Override the default backend |
Set Power
Turn a device on or off.
Tool: set_power
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
state |
string | Yes | on or off |
backend |
string | No | Override the default backend |
Set Brightness
Adjust a device's brightness level.
Tool: set_brightness
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
brightness |
integer | Yes | Brightness level (0-100) |
backend |
string | No | Override the default backend |
Set Color
Set a device to a specific color using RGB values.
Tool: set_color
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
r |
integer | Yes | Red (0-255) |
g |
integer | Yes | Green (0-255) |
b |
integer | Yes | Blue (0-255) |
backend |
string | No | Override the default backend |
Set Color Temperature
Set a device to a warm or cool white using color temperature.
Tool: set_color_temperature
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
temperature |
integer | Yes | Color temperature in Kelvin (2000-9000) |
backend |
string | No | Override the default backend |
List Scenes
List the built-in light scenes available for a device (e.g. "Rainbow", "Candlelight", "Ocean"). Use this to see what scene names you can activate. Requires the v2 backend.
Tool: list_scenes
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
List DIY Scenes
List the custom scenes you've created in the Govee Home app. Requires the v2 backend.
Tool: list_diy_scenes
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
Activate Scene
Activate a built-in or DIY scene by name. Use list scenes or list DIY scenes first to see available names. Requires the v2 backend.
Tool: activate_scene
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id |
string | Yes | The device ID |
model |
string | Yes | The device model |
scene_name |
string | Yes | The name of the scene to activate (exact match from the list) |
scene_type |
string | Yes | light for built-in scenes, diy for your custom scenes |
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。