Yeelight IoT MCP Server
Yeelight device discovery, state, control, and scene execution.
Connector by Yeelight · GitHub account verified by the MCP Registry
Install
Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install connector/yeelight-yeelight-iot-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Remote endpoint
https://api.yeelight.com/apis/mcp_server/v1/mcpRemote (HTTP)
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: api-integration
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 6 read · 1 write · 0 delete · 1 not yet classified
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- Nothing to install (hosted)
- Runs as
- Hosted (remote endpoint)
Tools by what they do 8
Read from the source code; the running server may list different tools.
Read 6 · Look things up without changing anything.
get_areasget_currnet_house_infoget_devicesget_groupsget_roomsget_scenes
Write 1 · Create, change, send or run things.
execute_scene
Not yet classified 1 · We could not tell from the name and description.
control_node
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
Authorization
Other settings (environment variables or headers).
House-IdYeelight-Region
Network hosts it talks to 5
api-de.yeelight.com· found in codeapi-dev.yeedev.com· found in codeapi-sg.yeelight.com· found in codeapi-us.yeelight.com· found in codeapi.yeelight.com· found in remote endpoint, install command, code
Tools (8)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
control_node# 工具用途:节点控制 - 家庭、区域、房间、设备组、设备都被视为"节点",其类型通过 nodeType 区分。 - 节点控制请求中的 nodeId 是节点的唯一标识。用户通常提供的是节点名称,因此在调用控制接口前,必须先使用相应工具获取节点nodeId,nodeId可以是家庭ID,区域ID,房间ID,设备组ID,设备ID,确认后再执行控制操作。 - 节点控制指令通过 command 区分不同的操作。 - 控制指令中参数的 value 类型需与节点属性值的类型一致。 - 在调用此接口之前,请先确认节点支持的属性及其对应的可操作类型。如果目标节点不支持该属性,则无法进行控制。 - 控制指令中的propName(**参数名称propName请勿传错**)参数,必须填写节点属性列表中对应属性的 propId 字段值,如 p(开关)、c(颜色)、ct(色温)、l(亮度)、tp(窗帘开合度)等。应根据节点属性列表中支持的 propId 选择最合适的属性来进行控制操作。 ## 控制节点说明 家庭、区域、房间、设备组、设备都被视为"节点",其类型通过 nodeType 区分。 例如: - "关闭所有灯"的请求,可视为关闭家庭下所有的灯,可以使用家庭节点类型来实现。 - "打开客厅灯"的请求,可以使用房间节点类型来实现。 ### 节点类型(nodeType)信息列表 | 节点类型(node…
execute_scene# 工具用途:执行情景(场景、模式)。 - 在执行情景(场景、模式)前,必须确保已获取到对应的情景ID。由于用户通常提供的是情景名称,因此请务必先通过相应的工具获取情景ID,再使用该ID执行情景操作。 - 默认 dryRun=true,只返回执行计划,不调用真实执行接口。 - 如需真实执行,必须显式传 dryRun=false 且 confirmSideEffect=true。
get_areas获取当前用户家庭(项目)下所有的区域
get_currnet_house_info获取用户当前家庭(或项目)的信息
get_devices获取当前用户家庭(项目)下所有的设备或者获取某个房间下的设备
get_groups获取当前用户家庭(项目)下所有的设备组或者获取某个房间下的设备组(设备组:相同设备类型的设备可以组成设备组,例如灯组、开关组灯)
get_rooms获取当前用户家庭(项目)下所有的房间
get_scenes获取当前用户家庭(项目)下所有的情景(场景、模式)
Signals
- Stars
- 10
- Forks
- 2
- Open issues
- 0
- Last commit
- Jul 23, 2026 (3 months ago)
- Last release
- Oct 12, 2026 (18 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.Yeelight/yeelight-iot-mcp- Version
- 0.1.0
- Auth
- Bearer token
- License
- Apache-2.0
- Repository
- github.com/Yeelight/yeelight-iot-mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from Yeelight
Cite this page
Yeelight IoT MCP Server. Agent Mart. https://agentmart.dev/connectors/yeelight-yeelight-iot-mcp (last updated 2026-10-24)