Yeelight home metadata and guarded management workflows.
Connect Remote server
claude mcp add --transport http yeelight-metadata-mcp https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>" --header "Yeelight-Region: <YEELIGHT_REGION>" --header "House-Id: <HOUSE_ID>"
{
"mcpServers": {
"yeelight-metadata-mcp": {
"url": "https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>",
"Yeelight-Region": "<YEELIGHT_REGION>",
"House-Id": "<HOUSE_ID>"
}
}
}
}
{
"servers": {
"yeelight-metadata-mcp": {
"type": "http",
"url": "https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>",
"Yeelight-Region": "<YEELIGHT_REGION>",
"House-Id": "<HOUSE_ID>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Yeelight cloud Bearer token. |
Yeelight-RegionOptional | Optional Yeelight region: cn, sg, us, eu, or dev. |
House-IdOptional | Optional Pro home identifier for request-scoped selection. |
Details
| Endpoint | https://api.yeelight.com/apis/metadata_mcp_server/v1/mcp (Streamable HTTP) |
| First published | 12 Oct 2026 |
| Last updated | 12 Oct 2026 |
| Registry name | io.github.Yeelight/yeelight-metadata-mcp |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
