
Govee
io.github.evefromwayback由 GitHub 帳號 evefromwayback 發布v0.2.0更新於 Oct 27, 2026
LAN-first, cloud-fallback MCP server for Govee smart lights and devices.
概覽
優先走區域網路、雲端備援的 MCP 伺服器,讓助理依名稱探索並控制 Govee 智慧燈、插座與家電。
- 可以做什麼
- 探索裝置與群組,並重新整理所有裝置的即時狀態
- 讀取單一裝置或群組的電源、亮度與顏色狀態
- 開關裝置,設定亮度、RGB 顏色與白光色溫
- 列出並套用各裝置支援的動態情境(僅雲端)
- 建立、列出與刪除裝置群組,一個指令套用到所有成員
- 適用情境
- 當你希望 AI 助理在家庭網路上依好記的名稱控制 Govee 燈、插座或家電時使用;區域網路可達的裝置走本機控制,其餘透過 Govee 雲端 API。
- 執行需求
- 以本機 Python 套件執行(需 Python 3.10 以上,可透過 uvx 或 govee-mcp 指令啟動)。雲端控制、插座、家電與情境需要選用的 GOVEE_API_KEY;只用區域網路燈具時不需金鑰。區域網路控制需在 Govee Home 應用程式為每台裝置開啟 LAN Control,並允許網路通過 UDP 埠 4001、4002、4003。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Govee,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
govee-mcp
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.
It is built to run on a home network. It prefers local LAN control for lights (fast, no internet, no rate limits) and falls back to Govee's cloud API for plugs, appliances, and anything not reachable on the LAN.
Status and spirit
This is a v0 that works for me on my own network. It is shared in the spirit of "here is something that works with an agent on my home network, have it, make it yours, and harden it as you please." It is not a supported product. Issues and pull requests are welcome, but treat it as a starting point rather than a finished appliance.
What it does (v0)
- 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.
- Stays under Govee's published cloud limits (100 requests per minute, 10000 per day) with a client-side guard.
What it does not do yet (the "harden it" list)
- Bluetooth temperature and humidity sensors (for example the H5075). Those are read over BLE, not the cloud or LAN API, and are the most interesting next step.
- Per-segment color, music mode, and DIY effects. Scenes are supported; these are the remaining cloud capabilities.
- Real-time push state (Govee's AWS IoT channel).
These are deliberately left as room to grow.
How it compares
The existing Govee MCP servers are thin: one is cloud-only and controls a single hardcoded device with three tools; another is LAN-only and lights-only. This one does multi-device discovery, both transports with automatic selection, state read-back, and cloud rate-limit handling.
Requirements
- 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.
Install
From source:
This installs a govee-mcp command. To run without installing:
Configure
Copy .env.example to .env and fill in what you need, or set the variables in your MCP client config.
Command-line use
A small CLI ships alongside the server and uses the same engine, so it is the fastest way to confirm things work before wiring up an MCP client. Start with doctor.
Run govee help, or just govee with no arguments, for the command reference. doctor reports whether your key loaded, how many devices are on your cloud account, and how many answered on the LAN, with a hint for whatever is missing. If govee is not on your PATH, use python3 -m govee_mcp.cli ... instead.
Any device name in the control commands can also be a group name. Define a group with govee group "Living Room" "Bulb 1" "Bulb 2", then govee on "Living Room", govee color "Living Room" 255 0 0, or govee state "Living Room" apply to every device in it. Groups are stored in ~/.config/govee-mcp/groups.json (override with GOVEE_GROUPS_PATH).
govee devices is instant: it lists devices from the cache and makes no live calls. govee refresh re-scans your devices and then prints the live state of all of them. govee state (with or without a name) is always a live read.
Connect an MCP client
Claude Desktop (claude_desktop_config.json), installed command:
Running from source instead:
Use with Hermes Agent
Hermes Agent has a native MCP client, so this server drops in. Once it is in the Hermes catalog, install it by name:
To wire it manually, add it under mcp_servers in your Hermes config and put GOVEE_API_KEY in your Hermes .env (the server process inherits it):
If govee-mcp is not on the launch PATH, use its absolute path or python3 -m govee_mcp. A Hermes catalog manifest is included at hermes/manifest.yaml.
Tools
list_devices(): discovered devices with names, supported actions, and transports. Call this first.list_groups(): device groups and their members.create_group(name, devices): create or replace a group.delete_group(name): delete a group.get_device_state(name): current power, brightness, and color.refresh(): re-scan devices and return the live state of all of them.set_power(name, on): turn on or off.set_brightness(name, level): 0 to 100.set_color(name, red, green, blue): each channel 0 to 255.set_color_temp(name, kelvin): roughly 2000 (warm) to 9000 (cool).list_scenes(name): the dynamic scenes (preset effects) a device supports.set_scene(name, scene): apply a scene by name. Calllist_scenesfirst to get valid names.
Every control tool's name can be a single device or a group name (see list_groups); a group applies the action to all its members.
Scenes (the "patterns": Sunrise, Aurora, and so on) are cloud-only and differ per device, so they need an API key and are fetched live from each device rather than hardcoded. The other actions work over both transports. Each control tool returns a structured result. A change is only real when the tool returns ok=true; the tool descriptions instruct the model not to claim a change happened without a successful call.
How transport selection works
On each action the registry picks a transport:
- If the device was found on the LAN, LAN control is preferred (local and unmetered) for the light actions it supports.
- Otherwise the cloud API is used. This is required for plugs, appliances, and devices without LAN control.
Set GOVEE_PREFER_LAN=false to always use the cloud, or disable a transport entirely with GOVEE_LAN_ENABLED=false or GOVEE_CLOUD_ENABLED=false.
API terms and when you need a key
Govee's cloud Developer API is free but, per Govee, for non-commercial use only. You may not use it for profit-making purposes or charge anyone for an implementation built on it. That restriction is on the cloud service and applies to whoever supplies the key, not to this code. Personal home use and sharing this project for free are both fine. Do not build a paid product on the free key without arranging commercial terms with Govee. See Govee's API service terms: https://app-h5.govee.com/common/api-service-item
You do not always need a key:
- LAN mode needs no key and never contacts Govee's servers. If you only have lights, enable LAN Control on each one and run with
GOVEE_CLOUD_ENABLED=false. - The key is what lets the server reach devices Govee does not expose over the LAN (plugs, appliances), fall back when a light is not reachable on the LAN, and pull friendly names and capabilities from your account. LAN discovery alone only returns a MAC, an IP, and a model number.
Security notes, and on vendoring vs cloning
- This server takes no third-party device library as a runtime dependency. The Govee LAN and cloud protocols are reimplemented here from Govee's public protocol documentation. The only runtime dependency is the official MCP SDK (MIT). That keeps the supply-chain surface tiny: you run your own code plus one well-known SDK.
- If you extend this with an existing Govee library later (for example for Bluetooth sensors), prefer vendoring a pinned, inspected copy over depending on it live. Vendoring means you read exactly what runs, it cannot change under you, and you can trim it to what you need. The cost is that you own its updates. Only vendor permissively licensed code, since vendoring copyleft code would relicense this project.
- Your API key is read from the environment and never logged. Do not commit your
.env. - LAN control uses unauthenticated UDP on your local network, which is how Govee's LAN API works. Keep IoT devices on a trusted or segmented network.
- No telemetry. The server talks only to your devices and, when used, Govee's API.
Testing
The tests mock the cloud HTTP layer and run a local fake Govee device over UDP, so they need no API key and no real hardware.
License and attribution
MIT. See LICENSE.
The protocols were implemented from Govee's public LAN guide and Developer API v2 documentation. Thanks to the open-source projects that mapped this territory first (govee2mqtt and govee-led-wez, homebridge-govee, and the Govee BLE sensor projects). No code was copied from them; they are credited as references.
Roadmap
- v1: Bluetooth sensor reads (temperature and humidity), per-segment color, music mode, and optional real-time state.
來源:README.md,提交 9847417
工具
0版本歷史
1- v0.2.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分