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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.