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

Related MCP server: Home Assistant MCP Server

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.

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

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

Set Power

Turn a device on or off.

Tool: set_power

Set Brightness

Adjust a device's brightness level.

Tool: set_brightness

Set Color

Set a device to a specific color using RGB values.

Tool: set_color

Set Color Temperature

Set a device to a warm or cool white using color temperature.

Tool: set_color_temperature

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

List DIY Scenes

List the custom scenes you've created in the Govee Home app. Requires the v2 backend.

Tool: list_diy_scenes

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

License

MIT