LIFX API MCP Server

@furey

Basic information

About LIFX API MCP Server

🤖💡 MCP Server for LIFX API

LIFX API MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "lifx-api-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "lifx-api-mcp-server@latest"
      ]
    }
  }
}

LIFX API MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is LIFX API MCP Server?

LIFX API MCP Server is a local Model Context Protocol (MCP) server that provides access to LIFX smart devices using natural language via LLMs. It allows users to list lights, set states, activate scenes, and trigger effects through the LIFX HTTP API.

How to use LIFX API MCP Server?

Obtain a LIFX API token from the LIFX Cloud settings page. Install the server via npx (npx -y lifx-api-mcp-server@latest) or Docker (docker run --rm -i --network=host furey/lifx-api-mcp-server). Configure the token using a config file (~/.lifx-api-mcp-server.jsonc), environment variable (CONFIG_API_TOKEN), or command-line argument. Set up an MCP client (e.g., Claude Desktop) and control lights using natural language. Use resources like lifx://lights and prompts like effect-creator.

Key features of LIFX API MCP Server

18 tools for LIFX device control and scene management
Live resources: light list, light state, and scenes
Prompts: effect-creator, troubleshooter, selector-helper
Config file customization with component disabling
Supports Docker, NPX, and source-based installation
Uses standard LIFX selectors and color strings

Use cases of LIFX API MCP Server

Control LIFX lights using natural language through an LLM client.
Automate scene activation or light effects without manual scripting.
Diagnose connectivity issues for specific lights with the troubleshooter prompt.
Build custom light states and cycles for home automation.
Integrate LIFX control into AI-driven workflows and assistants.

Frequently asked questions

What are the runtime requirements?

Node.js v18+ (for NPX/source install) or Docker (for Docker install). A LIFX API token is required.

How do I configure the API token?

Set it via the config file (`apiToken` field in `~/.lifx-api-mcp-server.jsonc`), environment variable (`CONFIG_API_TOKEN`), or command-line argument (least recommended). Priority follows that order.

Does the server store any data?

No. The server does not store or cache information permanently; all device data remains in the LIFX cloud.

What transport does the server use?

It uses stdio transport, as shown in the startup log output ("Creating stdio transport").

Can I disable specific tools, resources, or prompts?

Yes. Use the `disabled` or `enabled` keys in the config file to selectively disable or limit components.

Comments

More Developer Tools MCP servers

Modelglass

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

Unipile

unipile

Unipile MCP server: LinkedIn MCP (Sales Navigator, Recruiter), WhatsApp, Instagram, Telegram and email MCP for coding agents. Build your LinkedIn, WhatsApp and email API integration from Cursor, Claude Code, Codex.

SSH MCP Server

hypnosis

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

offprompt

MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

Moxie Docs

Jackalope-Dev

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.