LIFX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIFX_API_TOKEN | Yes | Your LIFX API token from https://cloud.lifx.com/settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_lightsC | Get lights belonging to the authenticated account |
| set_stateC | Set the state of lights |
| toggle_powerC | Toggle power state of lights |
| breathe_effectC | Perform a breathe effect |
| pulse_effectC | Perform a pulse effect |
| list_scenesC | List all scenes available in the account |
| activate_sceneC | Activate a scene |
| validate_colorC | Validate a color string |
| effects_offC | Turn off any running effects |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| LIFX API Documentation | Complete LIFX API endpoint documentation |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as list_lights vs. set_state, but breathe_effect and pulse_effect could be confused as both are light effects. The descriptions are clear, but the overlap in effect types might cause occasional misselection.
All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., activate_scene, list_lights, toggle_power). There are no deviations in naming conventions, making the set predictable and readable.
With 9 tools, the count is well-scoped for a LIFX lighting control server. It covers core operations like listing, state management, effects, and scenes without being overwhelming or too sparse.
The toolset provides good coverage for light control, including listing, state changes, effects, and scenes. A minor gap is the lack of a dedicated tool for deleting or managing scenes beyond activation, but agents can likely work around this using existing tools.