Govee MCP Server

LAN-first, cloud-fallback MCP server for Govee smart lights and devices. That is what the govee mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A LAN-first, cloud-fallback Model Context Protocol (MCP) server for Govee smart devices. Point an AI agent, or any MCP client, at your Govee lights, plugs, and appliances and control them by name.

• Discovers your devices (cloud account list plus a LAN scan) and addresses them by friendly name
• Controls power, brightness, RGB color, and white color temperature
• Reads current device state (power, brightness, color)
• Lists and applies dynamic scenes (preset effects), fetched live per device (cloud-only)
• Groups devices so one command (on/off, color, scene, state) applies to every member
• Prefers LAN for LAN-capable lights and falls back to the cloud for everything else

What it needs from you

Configuration is passed through the environment: GOVEE_API_KEY, PYTHONPATH, GOVEE_CACHE_PATH, GOVEE_GROUPS_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.10 or newer. - A Govee API key for cloud control (optional, but needed for plugs, appliances, and non-LAN devices). Get one in the Govee Home app: Profile, then About Us, then Apply for API Key. - For LAN control: enable "LAN Control" on each device in the Govee Home app, and make sure UDP ports 4001, 4002, and 4003 can pass on your network.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by evefromwayback; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.