LIFX LAN MCP

by simon-duchastel

141 downloads
Not rated
GitHub

About

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

Details

Author
simon-duchastel
Downloads
141
Categories
Other

- 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)

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name LIFX LAN MCP
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

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.

lifx_lan_list_lights

List all Lifx lights currently available on the user's local area network (LAN).Each light is specified by a unique string label.Use this to get which lights the user wants to interact with, as the label is used in other tools to interact with lights.Also includes additional information about the light, such as group and location

lifx_lan_get_lights_state

Get the current state of one or more LIFX lights, including their colors, whether they're on or off, and what groups and locations they belong to (if any).

lifx_lan_set_lights_color

Set the color of one or more Lifx lights. Must specify hue, saturation, brightness, and may optionally specify kelvin temperature (otherwise 3500 is used).

lifx_lan_turn_on_lights

Turn on one or more Lifx lights, optionally at specific color.

lifx_lan_turn_off_lights

Turn off one or more Lifx lights.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "lifx lan mcp": {
            "lifx-lan-mcp": {
                "command": "npx",
                "args": [
                    "-y",
                    "lifx-lan-mcp"
                ]
            }
        }
    }
}

McpServers

{
    "lifx-lan-mcp": {
        "command": "npx",
        "args": [
            "-y",
            "lifx-lan-mcp"
        ]
    }
}

LIFX LAN MCP

Cover image

npm MCP Server Buy Me A Coffee

A Model Context Protocol (MCP) server for allowing an LLM to control LIFX lights over your local area network (LAN), without cloud connectivity.

Note that the MCP server must be running on the same wifi network as your LIFX lights in order for the tool to work.

Features

- List all available LIFX lights on your network
- Get the current state of lights (color, on/off, labels)
- Turn lights on/off
- Change light colors
- Local network operation (no cloud required, server must be running on the same network)
- Configurable transport (sse or stdio)

Installation

NPX (configuring via local stdio) - default

Add this, or similar, to your LLM MCP config file (ex. for Claude Desktop this is claude_desktop_config.json).

{
  "mcpServers": {
    "lifx-lan-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "lifx-lan-mcp"
      ]
    }
  }
}

Running the Server

The server can be run in two modes: stdio (default) or HTTP server mode. The server supports both the 2025-03-26 and 2024-11-05 protocol versions.

Stdio Mode (Default)

Stdio mode is the simplest way to run the server, where it communicates directly with the LLM through standard input/output. This is the default mode and requires no additional configuration. In this mode, the MCP server
is started directly by the client with which it's communicating.

```bash

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.