Yeelight IoT MCP
Officialby Yeelight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| House-Id | No | Optional House ID header. When omitted, the server selects the first Pro home in that Region. | |
| Authorization | Yes | Required Yeelight Authorization token for the request header. The server accepts a raw token or a value prefixed with Bearer. | |
| Yeelight-Region | No | Optional Yeelight region header. When omitted, a JWT Region claim selects the official endpoint. | |
| YEELIGHT_IOT_MCP_PATH | No | Streamable HTTP path. | /mcp |
| YEELIGHT_IOT_MCP_LOG_DIR | No | Log directory. | ./logs/yeelight-online-iot-mcp-server |
| YEELIGHT_IOT_MCP_BIND_HOST | No | Bind address. Defaults to 127.0.0.1 in local/test; production defaults to 0.0.0.0. | |
| YEELIGHT_IOT_MCP_API_BASE_URL | No | Yeelight API origin. | https://api.yeelight.com |
| YEELIGHT_IOT_MCP_HTTP_TIMEOUT | No | Upstream timeout in seconds. | 15 |
| YEELIGHT_IOT_MCP_NACOS_ENABLED | No | Enable optional service registration. | false |
| YEELIGHT_IOT_MCP_DEFAULT_REGION | No | Fallback Region for opaque tokens. | cn |
| YEELIGHT_IOT_MCP_FETCH_NODES_MAX_SIZE | No | Maximum list page size. | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessOutdated data