CP server (light names, states, scene names) will be sent to the LLM provider. Be mindful of potentially sensitive information in your light/group/location/scene labels if privacy is a major concern. * **Local Execution:** This server runs locally on your machine. It communicates directly with the LIFX cloud API over HTTPS. ## Tutorial Ensure the server is running and connected to your MCP client. Replace placeholders like `label:MyLamp` with your actual light/group/location labels or IDs. 1. **Check Available Lights (Resource):** * `@lix-api:lifx://lights` * ^{➥ Uses `lights` resource} 2. **Get Specific Light State (Resource):** * `@lix-api:lifx://light/label:Office Lamp/state` * ^{➥ Uses `light-state` resource} 3. **Get Available Scenes (Resource):** * `@lix-api:lifx://scenes` * ^{➥ Uses `scenes` resource} 4. **Use Selector Helper (Prompt):** * `@lix-api:selector-helper goal: "the lights in the kitchen"` * ^{➥ Uses `selector-helper` prompt} 5. **Create an Effect (Prompt):** * `@lix-api:effect-creator effect_type:breathe selector:all description:"a very slow fade to warm white"` * ^{➥ Uses `effect-creator` prompt (follow instructions in response)} 6. **Troubleshoot a Light (Prompt):** * `@lix-api:troubleshooter selector:"id:d073d5xxxxxx"` * ^{➥ Uses `troubleshooter` prompt} 7. **List Your Lights (Tool):** * _"list my lights"_ or _"list lights selector:all"_ * ^{➥ Uses `list-lights` tool} 8. **Turn a Light On (Tool):** * _"turn on the lamp named Office Lamp"_ or _"set state selector:label:Office Lamp power:on"_ * ^{➥ Uses `set-state` tool} 9. **Set Color and Brightness (Tool):** * _"set the Kitchen group lights to blue at 50% brightness over 3 seconds"_ * _"set state selector:group:Kitchen color:blue brightness:0.5 duration:3"_ * ^{➥ Uses `set-state` tool} 10. **Toggle a Location (Tool):** * _"toggle the lights in the Living Room"_ or _"toggle power selector:location:Living Room"_ * ^{➥ Uses `toggle-power` tool} 11. **Increase Brightness (Tool):** * _"make all lights 10% brighter"_ or _"state delta selector:all brightness:0.1"_ * ^{➥ Uses `state-delta` tool} 12. **Activate a Scene (Requires Scene UUID from Resource/Tool):** * _"activate scene with uuid abcdef12-3456-..."_ * _"activate scene scene_uuid:abcdef12-3456-..."_ * ^{➥ Uses `activate-scene` tool} ## Dockerfile ```dockerfile FROM node:18-alpine WORKDIR /app # Copy package files COPY package*.json ./ # Install dependencies cleanly # Using --omit=dev because devDependencies are not needed in production RUN npm ci --omit=dev --production --no-fund --no-audit # Copy the rest of the application code COPY . . # Set the entrypoint ENTRYPOINT ["node", "lifx-api-mcp-server.js"] # Default command (can be overridden, e.g., with API token if not using config/env) # CMD ["YOUR_DEFAULT_TOKEN_IF_NEEDED"] ``` ## Disclaimer * This software is provided "as is", without warranty of any kind. Use at your own risk. * The author is not affiliated with LIFX (LiFi Labs Inc.). * Ensure you understand the LIFX API rate limits (120 requests/minute per token) to avoid temporary blocks. Rate limit information is logged if `logLevel` is `verbose`. * This server was partially generated with AI assistance and may contain bugs. ## Support If you find this tool useful, consider supporting the developer (optional): [Buy Me a Coffee](https://www.buymeacoffee.com/furey) | [GitHub Sponsorship](https://github.com/sponsors/furey)2a:T625,## What is LIFX API MCP Server? LIFX API MCP Server is a local Model Context Protocol (MCP) server that allows users to control LIFX smart lighting devices using natural language through LLMs, enabling actions such as listing lights, setting states, activating scenes, and triggering effects via the LIFX HTTP API. ## How to use LIFX API MCP Server? To u

LIFX API MCP Server

Comments