MCP.so
Sign In

LIFX API MCP Server

@furey

Repository

About LIFX API MCP Server

🤖💡 MCP Server for LIFX API

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"
      ]
    }
  }
}

Tools

No tools detected

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.

FAQ from LIFX API MCP Server

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.

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

Basic information

Category

Developer Tools

License

MIT

Transports

stdio

Author

furey

More Developer Tools MCP servers

S

SecondSim

econdSim provisions real UK mobile numbers (non-VoIP) via eSIM, built for freelancers, sole traders, small businesses, and enterprise teams. Unlike VoIP apps and virtual numbers, SecondSim numbers register as genuine phy

BetterBugs

BetterBugs

The BetterBugs MCP (Model Context Protocol) enables you to load BetterBugs bug reports (via report links) directly to your preferred AI Agents and developer environments with MCP Client capabilities (such as Cursor, VS C

Vibgrate MCP

Vibgrate

Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

3

TranscriptFetch MCP Server

TranscriptFetch

Model Context Protocol (MCP) server for TranscriptFetch: fetch YouTube transcripts, search, channels, and playlists from any MCP client.

Foremerge

naw103

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

50