LIFX LAN MCP
@simon-duchastel
MCP (Model Context Protocol) server for allowing AI agents to interact with the Lifx lights on your LAN. Not officially affiliated with Lifx or Feit Electric
Overview
What is LIFX LAN MCP?
A Model Context Protocol (MCP) server that allows an LLM to control LIFX lights over the local area network (LAN) without cloud connectivity. It must run on the same WiFi network as the LIFX lights and targets users who want local, low‑latency smart light control through an AI assistant.
How to use LIFX LAN MCP?
Install via npx and add the provided JSON configuration to your LLM’s MCP config file (e.g., claude_desktop_config.json). The server can run in stdio mode (default, started directly by the client) or HTTP server mode (--mode sse). Tools include listing lights, getting state, setting color, turning lights on, and turning lights off – all invoked by the LLM.
Key features of LIFX LAN MCP
- List all available LIFX lights on the network
- Get current state (color, on/off, labels) of lights
- Turn lights on and off
- Change light colors with hue, saturation, brightness, and optional kelvin
- Operates locally – no cloud required
- Configurable transport: stdio or SSE (HTTP server mode)
Use cases of LIFX LAN MCP
- Voice‑controlled lighting via an LLM assistant
- Automated lighting scenes triggered by AI reasoning
- Dynamic color adjustments based on time or activity
- Home automation without relying on internet connectivity
- Natural‑language control of groups of lights
FAQ from LIFX LAN MCP
What are the runtime requirements?
Node.js, TypeScript, and LIFX lights on the same local WiFi network.
Does this server require an internet connection to work?
No. It communicates with LIFX lights over the local area network and does not use cloud services.
What transport modes are available?
Stdio (default, for direct client‑server communication) and SSE (HTTP server mode, for standalone network‑accessible operation).
Is authentication supported in HTTP server mode?
No. HTTP server mode currently lacks authentication; the README warns it is dangerous and recommends use at your own risk until authentication is added.
Which MCP protocol versions are supported?
Both the 2025‑04‑21 (latest) and 2025‑03‑26 (legacy) protocol versions are supported, using /mcp and /sse endpoints respectively.
