Yeelight Metadata MCP Server
Officialby Yeelight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METADATA_MCP_PATH | No | MCP route | /mcp |
| METADATA_MCP_PORT | No | Listen port | 9010 |
| METADATA_MCP_BIND_HOST | No | Listen address | 127.0.0.1 for local/test, 0.0.0.0 for prod/dev |
| METADATA_MCP_HOST_PREFIX | No | Yeelight API host | https://api.yeelight.com |
| METADATA_MCP_RUNTIME_ENV | No | Runtime environment: prod, dev, local, or test | prod |
| METADATA_MCP_API_BASE_URL | No | Explicit API base URL | host prefix |
| METADATA_MCP_HTTP_TIMEOUT | No | Upstream timeout in seconds | 15 |
| METADATA_MCP_NACOS_ENABLE | No | Nacos registration switch | environment-dependent |
| METADATA_MCP_NACOS_SERVER | No | Nacos servers | environment-dependent |
| METADATA_MCP_RESOURCE_DIR | No | Runtime catalog override | resources/catalog |
| METADATA_MCP_ALLOW_CANDIDATE_EXECUTION | No | Candidate execution gate | false |
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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yeelight/yeelight-metadata-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server