Skip to main content
Glama

LedFX MCP Server

A Model Context Protocol (MCP) server that enables AI assistants to interact with and control a local LedFX instance.

Overview

This MCP server provides a bridge between AI assistants (like Claude) and LedFX, allowing you to control your LED lighting setup through natural language. The server exposes LedFX's functionality as MCP tools that AI assistants can use to:

  • Query device and virtual information

  • List and manage LED devices and virtuals

  • Apply effects to virtuals (virtual LED strips)

  • Manage and activate scenes

  • Create custom palettes and playlists

  • Get AI-powered effect recommendations

  • Get system information

Related MCP server: MCP Govee

Features

  • šŸŽØ Control LED effects through natural language

  • šŸ”§ Manage multiple LED devices and virtuals

  • šŸŽ­ Activate pre-configured scenes

  • šŸ“Š Query device and system information

  • šŸ”’ Type-safe TypeScript implementation

  • šŸ—ļø Built following software design best practices

  • šŸŽØ LedFX colors & gradients via /api/colors (builtin + user-defined)

  • šŸ—‚ļø Palette management stored as user gradients in LedFX

  • šŸ¤– AI-powered scene creation from natural language descriptions

  • šŸ“ Playlist support for scene sequences

  • šŸ’” Effect recommendations based on mood and description

  • šŸ“š LedFX feature explanations - learn about any LedFX concept

  • šŸ”„ Correct API implementation - uses virtuals (not devices) for effects

Design Principles

This project follows principles from:

Grokking Simplicity

  • Separation of Concerns: Actions (I/O operations) are clearly separated from calculations (pure functions)

  • Stratified Design: Clear abstraction layers (tools → client → API)

  • Immutability: Data transformations use pure functions where possible

A Philosophy of Software Design

  • Deep Modules: Complex LedFX API interactions hidden behind simple interfaces

  • Information Hiding: Implementation details abstracted from callers

  • Minimize Complexity: Each module has a single, focused responsibility

āœ… Implementation Status

Current Status: Implemented with Comprehensive Test Suite

This MCP server is implemented against current LedFX APIs and validated with automated tests plus continuous integration checks. The implementation fixes critical API issues (virtuals vs devices) and adds advanced features like palette management, natural language scene creation, and AI-powered recommendations.

Important Notes

  1. API Corrections Applied: Effects are correctly applied to virtuals (not devices), matching current LedFX API behavior

  2. Comprehensive Testing: 34 tests covering unit and E2E scenarios - all passing

  3. CI/CD Pipeline: GitHub Actions workflow with lint, build, test, and coverage jobs

  4. Production Ready: Fully documented with installation guide, usage examples, and architecture docs

Documentation

Status: Ready for production use with LedFX 2.1.4+ (verified end-to-end against LedFX 2.1.9)

Prerequisites

  • Node.js 24 or 25

  • A running LedFX instance (default: localhost:8888)

  • An MCP-compatible AI assistant (e.g., Claude Desktop)

Running LedFX for Testing

Using Docker (Recommended):

# Using docker-compose (included in this repository)
docker-compose up -d

# Or using docker run
docker run -d --name ledfx -p 8888:8888 ledfxorg/ledfx:latest

Using pip:

pip install ledfx
ledfx --host 0.0.0.0 --port 8888

See the official LedFX links in REFERENCES.md for current installation docs.

Installation

# Clone the repository
git clone https://github.com/abossard/ledfx-mcp.git
cd ledfx-mcp

# Install dependencies
npm install

# Build and run in one command
npm run dev

Configuration

The server connects to LedFX using the following environment variables:

  • LEDFX_HOST: LedFX server host (default: localhost)

  • LEDFX_PORT: LedFX server port (default: 8888)

You can set these in your MCP client configuration or as environment variables.

Usage

Claude Desktop Configuration

Add the following to your Claude Desktop configuration file:

  • Claude Desktop launches this MCP server over stdio.

  • Use Node.js 24 or 25.

  • The path must be absolute when using node with dist/index.js.

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ledfx": {
      "command": "node",
      "args": ["/absolute/path/to/ledfx-mcp/dist/index.js"],
      "env": {
        "LEDFX_HOST": "localhost",
        "LEDFX_PORT": "8888"
      }
    }
  }
}

Auto-recompile on every start (recommended for development):

Using npm run start ensures the TypeScript source is recompiled (prestart hook) each time the MCP client launches the server, so you never run stale code:

{
  "mcpServers": {
    "ledfx": {
      "command": "npm",
      "args": ["run", "start", "--prefix", "/absolute/path/to/ledfx-mcp"],
      "env": {
        "LEDFX_HOST": "localhost",
        "LEDFX_PORT": "8888"
      }
    }
  }
}

If you prefer to run from Git without a local build, use npx as the command:

{
  "mcpServers": {
    "ledfx": {
      "command": "npx",
      "args": ["github:abossard/ledfx-mcp"],
      "env": {
        "LEDFX_HOST": "localhost",
        "LEDFX_PORT": "8888"
      }
    }
  }
}

Example Interactions

Once configured, you can interact with your LedFX setup through natural language:

Basic Operations:

  • "List all my LED virtuals"

  • "Activate the rainbow effect on my desk light virtual"

  • "Show me all available scenes"

  • "Clear effects from all virtuals"

Natural Language Scene Creation:

  • "Create a calm ocean scene with slow blue waves"

  • "Make an energetic party scene with fast rainbow colors"

  • "Create a romantic scene with dim pink and purple gradients"

  • "Build a focus scene with steady white light at medium brightness"

Color and Palette Management:

  • "List all LedFX colors and gradients"

  • "Get color or gradient 'sunset'"

  • "Create a user color 'my-magenta' = #FF00FF"

  • "Create a new palette called 'Sunset Vibes' with #FFA500, #FF69B4, #800080"

  • "Save a playlist of my party scenes"

Effect Recommendations:

  • "Recommend effects for a relaxing evening"

  • "What effects work well with music?"

  • "Suggest something energetic for a party"

Learning LedFX:

  • "Explain what virtuals are in LedFX"

  • "What's the difference between devices and virtuals?"

  • "How do audio-reactive effects work?"

  • "Tell me about WLED devices"

  • "List all available effect types"

Available Tools

The server exposes 85+ MCP tools organized into categories:

Core Management

Tool

Description

ledfx_get_info

Get LedFX server information (version, features)

ledfx_list_devices

List all physical LED devices

ledfx_get_device

Get details about a specific device

ledfx_list_virtuals

List all virtual LED strips (includes global paused state)

ledfx_get_virtual

Get details about a specific virtual

ledfx_activate_virtual

Activate/deactivate a virtual

ledfx_update_virtual_config

Update virtual config (transitions, brightness, frequency range, matrix)

ledfx_find_devices

Trigger network device discovery

ledfx_get_paused_state

Check if all virtuals are globally paused

ledfx_toggle_pause_all

Toggle global pause on all virtuals

ledfx_get_global_brightness

Get global brightness value (0-1)

ledfx_set_global_brightness

Set global brightness for all virtuals

ledfx_set_startup_scene

Set scene to activate on LedFX startup

ledfx_send_notification

Send notification to LedFX frontend UI

ledfx_get_now_playing

Get current Now Playing state (track metadata, artwork) and config

ledfx_update_now_playing

Update Now Playing config (gradient / track_text / album_art sections)

Effect Control (CORRECTED - uses virtuals)

Tool

Description

ledfx_set_effect

Apply an effect to a virtual (not device)

ledfx_update_effect

Update effect configuration

ledfx_clear_effect

Remove effects from a virtual

ledfx_get_effect_schemas

Get schemas for all effect types

Scene Management

Tool

Description

ledfx_list_scenes

List all available scenes

ledfx_activate_scene

Activate a pre-configured scene

ledfx_create_scene

Create new scene from current config

ledfx_delete_scene

Delete a saved scene

ledfx_create_scene_from_description

AI-powered scene creation from natural language

Palette Management (LedFX /api/colors)

Tool

Description

ledfx_list_palettes

List all palettes stored as user gradients

ledfx_create_palette

Create/update a palette (stored as user gradient)

ledfx_get_palette

Get palette by name

ledfx_delete_palette

Delete a palette by name

Playlist Management

Tool

Description

ledfx_list_playlists

List all playlists

ledfx_create_playlist

Create scene sequence playlist

ledfx_get_playlist

Get specific playlist

ledfx_delete_playlist

Delete a playlist

Color Management (LedFX /api/colors)

Tool

Description

ledfx_list_colors

List all colors and gradients from LedFX

ledfx_get_color_or_gradient

Get a specific color or gradient by ID

ledfx_upsert_color_or_gradient

Create/update a user color or gradient

ledfx_delete_color_or_gradient

Delete a user color or gradient

ledfx_delete_user_gradients

Delete all user-defined gradients (includes palettes)

AI Features

Tool

Description

ledfx_recommend_effects

Get effect recommendations based on mood/description

ledfx_explain_feature

Get detailed explanation of any LedFX feature

ledfx_list_features

List all explainable features

ledfx_list_effect_types

List all effect types with descriptions

Preset Management

Tool

Description

ledfx_get_presets

Get presets for a virtual's effect

ledfx_apply_preset

Apply a preset to a virtual

ledfx_save_preset

Save current effect as a user preset

ledfx_delete_preset

Delete a preset for a virtual

Audio Management

Tool

Description

ledfx_list_audio_devices

List audio input devices

ledfx_set_audio_device

Set active audio device

Development

# Install dependencies
npm install

# Build the project
npm run build

# Build and run in one command
npm run dev

# Watch mode for development
npm run watch

# Build and run in one command
npm run dev

# Lint the code
npm run lint

# Fix linting issues
npm run lint:fix

Project Structure

ledfx-mcp/
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ index.ts         # Main server entry point
│   ā”œā”€ā”€ ledfx-client.ts  # LedFX API client
│   └── tools.ts         # MCP tool definitions and handlers
ā”œā”€ā”€ docs/                # Comprehensive documentation
│   ā”œā”€ā”€ API_SPECIFICATION.md      # LedFX API reference
│   ā”œā”€ā”€ TEST_SPECIFICATION.md     # Test plans and requirements
│   ā”œā”€ā”€ IMPLEMENTATION_NOTES.md   # Known issues and fixes needed
│   └── REFERENCES.md             # LedFX resources and links
ā”œā”€ā”€ dist/                # Compiled JavaScript (generated)
ā”œā”€ā”€ docker-compose.yml   # Docker setup for testing
ā”œā”€ā”€ package.json         # Project configuration
ā”œā”€ā”€ tsconfig.json        # TypeScript configuration
└── README.md           # This file

Documentation

Comprehensive documentation is available in the docs/ directory:

API Specification

docs/API_SPECIFICATION.md

Complete reference for LedFX REST API endpoints (verified against LedFX 2.1.4 and upstream source):

  • All endpoint paths, methods, and parameters

  • Data model and orchestration caveats (virtuals, presets, scenes, playlists, blender)

  • API behavior quirks and compatibility notes

Test Specification

docs/TEST_SPECIFICATION.md

Comprehensive test requirements and test cases:

  • Unit test cases for all components

  • Integration test scenarios

  • End-to-end workflows

  • Performance test criteria

  • Compatibility test matrix

  • Mock strategies and test fixtures

  • Docker-based test environment setup

Implementation Notes

docs/IMPLEMENTATION_NOTES.md

Critical analysis of current implementation vs actual API:

  • Known issues and bugs (devices vs virtuals confusion)

  • Required fixes before production use

  • Missing features and functionality gaps

  • Recommended implementation phases

  • Migration path for future versions

References

docs/REFERENCES.md

Concise source index for API verification:

  • Official LedFX documentation links

  • Release/version links

  • Upstream source files used to validate API behavior

Architecture

The server is organized into three main layers:

  1. MCP Server Layer (index.ts): Handles MCP protocol communication

  2. Tools Layer (tools.ts): Defines available tools and routes requests

  3. Client Layer (ledfx-client.ts): Abstracts LedFX HTTP API interactions

This layered architecture ensures:

  • Clear separation of concerns

  • Easy testing and maintenance

  • Extensibility for new features

Contributing

Contributions are welcome! Please ensure your code:

  • Follows the existing code style

  • Includes appropriate comments

  • Passes linting (npm run lint)

  • Builds successfully (npm run build)

License

MIT License - see LICENSE file for details

Resources

Troubleshooting

Server won't connect to LedFX

  • Ensure LedFX is running and accessible at the configured host/port

  • Check firewall settings

  • Verify the LEDFX_HOST and LEDFX_PORT environment variables

Tools not appearing in Claude

  • Restart Claude Desktop after configuration changes

  • Verify the path to dist/index.js is absolute

  • Check Claude Desktop logs for errors

Support

For issues and questions:

Available Tools

83 tools
ledfx_activate_sceneB

Activate a saved scene by ID

Inputs: scene_id (required).

ledfx_activate_virtualA

Activate or deactivate a virtual. Virtuals must be active to display effects.

Inputs: virtual_id (required), active (required).

ledfx_add_scene_to_playlistB

Add a scene to an existing playlist

Inputs: playlist_id (required), scene_id (required), duration_ms.

ledfx_apply_globalA

Apply global config (gradient, brightness, background_color, flip, mirror) to all active effects. Optionally filter by virtual IDs.

Inputs: gradient, brightness, background_color, background_brightness, +3 more.

ledfx_apply_global_effectB

Apply a specific effect type and config to multiple virtuals at once. Bulk effect application.

Inputs: effect_type (required), effect_config, virtuals, fallback.

ledfx_apply_presetC

Apply a preset to a virtual

Inputs: virtual_id (required), category (required), effect_id (required), preset_id (required).

ledfx_clear_all_effectsA

Clear all active effects on all virtuals. Clean slate for authoring.

Inputs: no named parameters.

ledfx_clear_effectB

Clear/stop the current effect on a virtual

Inputs: virtual_id (required).

ledfx_create_backupA

Create a complete backup of LedFX configuration (virtuals, scenes, playlists, audio). Optionally saves to a local file path.

Inputs: file_path, description.

ledfx_create_integrationB

Create a new integration instance (e.g. QLC+ DMX bridge)

Inputs: type (required), config (required).

ledfx_create_paletteB

Create or update a palette by saving a user gradient in LedFX /api/colors.

Inputs: name (required), colors (required).

ledfx_create_playlistC

Create a new LedFX playlist with scenes

Inputs: id (required), name (required), scene_ids (required), mode, +1 more.

ledfx_create_qlc_eventA

Map a LedFX event to a QLC+ widget payload. When the event fires, the payload is sent to QLC+ via WebSocket.

Inputs: integration_id (required), event_type (required), event_filter (required), qlc_payload (required).

ledfx_create_sceneB

Create a new scene from current virtual configurations

Inputs: name (required), tags.

ledfx_create_scene_from_descriptionA

Create a scene from a natural language description (e.g., 'calm blue ocean waves' or 'energetic party rainbow')

Inputs: description (required), virtual_ids.

ledfx_deactivate_sceneA

Deactivate a scene without clearing all effects. Reverses scene activation.

Inputs: scene_id (required).

ledfx_delete_color_or_gradientA

Delete a user-defined color or gradient by ID in LedFX /api/colors.

Inputs: id (required).

ledfx_delete_effect_historyA

Delete a specific effect type from a virtual's effect history. Clears the effect if currently active.

Inputs: virtual_id (required), effect_type (required).

ledfx_delete_integrationA

Delete an integration and all its configuration

Inputs: integration_id (required).

ledfx_delete_paletteB

Delete a palette by name (removes the user gradient from LedFX /api/colors).

Inputs: name (required).

ledfx_delete_playlistC

Delete a LedFX playlist

Inputs: playlist_id (required).

ledfx_delete_presetB

Delete a preset for a virtual's effect

Inputs: virtual_id (required), category (required), effect_id (required), preset_id (required).

ledfx_delete_qlc_eventB

Delete a QLC+ event mapping permanently

Inputs: integration_id (required), event_type (required), event_filter (required).

ledfx_delete_sceneB

Delete a saved scene

Inputs: scene_id (required).

ledfx_delete_user_gradientsA

Delete all user-defined gradients in LedFX /api/colors (includes palettes).

Inputs: no named parameters.

ledfx_delete_virtualA

Delete a virtual and its associated device. Removes references from all scenes.

Inputs: virtual_id (required).

ledfx_explain_featureB

Get detailed explanation of a LedFX feature or concept

Inputs: feature (required).

ledfx_find_devicesA

Trigger network device discovery to find new LED devices (WLED, etc.)

Inputs: no named parameters.

ledfx_get_color_or_gradientA

Get a single color or gradient by ID from LedFX /api/colors.

Inputs: id (required).

ledfx_get_configA

Get full LedFX configuration JSON. Optionally filter to specific sections (audio, melbanks, wled_preferences, etc.).

Inputs: keys.

ledfx_get_deviceB

Get detailed information about a specific LED device

Inputs: device_id (required).

ledfx_get_effect_schemaA

Get the schema for a single effect type

Inputs: effect_type (required).

ledfx_get_effect_schemasA

Get schemas for all available effect types with their parameters

Inputs: no named parameters.

ledfx_get_global_brightnessA

Get the global brightness value (0-1) that applies to all virtuals

Inputs: no named parameters.

ledfx_get_infoB

Get information about the LedFX server including version and configuration

Inputs: no named parameters.

ledfx_get_paletteA

Get a palette by name (stored as a user gradient in LedFX /api/colors).

Inputs: name (required).

ledfx_get_paused_stateA

Check whether all virtuals are globally paused

Inputs: no named parameters.

ledfx_get_playlistB

Get a specific LedFX playlist by ID

Inputs: playlist_id (required).

ledfx_get_playlist_statusA

Get the status of the currently playing LedFX playlist

Inputs: no named parameters.

ledfx_get_presetsA

Get available presets for a virtual's current effect

Inputs: virtual_id (required).

ledfx_get_qlc_infoA

Get QLC+ integration details: available widgets, event types (Effect Set, Effect Cleared, Scene Activated), and configured event listeners

Inputs: integration_id (required).

ledfx_get_sceneB

Get a single scene by ID with full scene config payload

Inputs: scene_id (required).

ledfx_get_virtualC

Get detailed information about a specific virtual

Inputs: virtual_id (required).

ledfx_import_configA

Import a complete LedFX configuration (with version migration). Creates backup first. Triggers restart.

Inputs: config (required).

ledfx_list_audio_devicesA

List available audio input devices

Inputs: no named parameters.

ledfx_list_colorsA

List all colors and gradients from LedFX /api/colors. Returns LedFX native response types.

Inputs: no named parameters.

ledfx_list_devicesA

List all physical LED devices configured in LedFX (WLED, OpenRGB, etc.)

Inputs: no named parameters.

ledfx_list_effect_typesA

List all available effect types with descriptions, audio-reactivity, gradient support, 2D flag, and blender role recommendations. Use this to choose effects for blenders.

Inputs: filter_role, audio_reactive_only.

ledfx_list_featuresA

List all explainable LedFX features organized by category

Inputs: no named parameters.

ledfx_list_integrationsA

List all integration instances (QLC+, Spotify, etc.) with their status and config

Inputs: no named parameters.

ledfx_list_palettesA

List all palettes stored as user gradients in LedFX /api/colors.

Inputs: no named parameters.

ledfx_list_playlistsA

List all playlists stored in LedFX

Inputs: no named parameters.

ledfx_list_scenesA

List all saved scenes. Scenes are complete lighting configurations.

Inputs: no named parameters.

ledfx_list_virtualsA

List all virtual LED strips. Virtuals are logical strips where effects are applied.

Inputs: no named parameters.

ledfx_patch_playlist_itemsC

Patch playlist items with add/remove/move/replace_duration operations

Inputs: playlist_id (required), operation (required), scene_id, index, +2 more.

ledfx_powerB

Shutdown or restart LedFX

Inputs: action (required), timeout.

ledfx_recommend_effectsC

Get effect recommendations based on description or mood

Inputs: description (required), mood.

ledfx_refresh_blender_scenesA

Recreate all blender scenes using their stored virtual configurations (no scene activation)

Inputs: no named parameters.

ledfx_rename_sceneB

Rename an existing scene

Inputs: scene_id (required), name (required).

ledfx_reset_configA

Reset LedFX configuration to defaults. Creates backup first. Triggers restart.

Inputs: no named parameters.

ledfx_restore_backupB

Restore LedFX configuration from a backup JSON. Can selectively restore virtuals, scenes, and/or playlists.

Inputs: backup (required), restore_virtuals, restore_scenes, restore_playlists, +3 more.

ledfx_save_presetA

Save the current effect configuration on a virtual as a user preset

Inputs: virtual_id (required), preset_name (required).

ledfx_send_notificationB

Send a notification to the LedFX frontend UI

Inputs: title (required), text (required).

ledfx_set_audio_deviceB

Set the active audio input device

Inputs: device_index (required).

ledfx_set_blenderA

Safely set a blender effect by configuring source virtuals first. Blender mixes background + foreground using a mask; mask should be audio reactive, and at least one of background/foreground should be audio reactive. Static colors are rarely useful.

Inputs: blender_virtual_id (required), background (required), foreground (required), mask (required), +1 more.

ledfx_set_effectA

Set an effect on a virtual (NOT a device). Effects control how LEDs display. Use ledfx_set_blender for blender.

Inputs: virtual_id (required), effect_type (required), effect_config, fallback.

ledfx_set_global_brightnessA

Set the global brightness for all virtuals (0-1)

Inputs: brightness (required).

ledfx_set_startup_sceneA

Set which scene activates automatically when LedFX starts

Inputs: scene_id (required).

ledfx_start_playlistC

Start playing a LedFX playlist

Inputs: playlist_id (required).

ledfx_stop_playlistA

Stop the currently playing LedFX playlist

Inputs: no named parameters.

ledfx_toggle_integrationB

Activate or deactivate an integration by ID

Inputs: integration_id (required).

ledfx_toggle_pause_allA

Toggle global pause on all virtuals. Returns new paused state.

Inputs: no named parameters.

ledfx_toggle_qlc_eventA

Enable or disable a QLC+ event mapping without deleting it

Inputs: integration_id (required), event_type (required), event_filter (required).

ledfx_trigger_fallbackB

Trigger the fallback mechanism on a virtual, reverting it to its default/previous effect

Inputs: virtual_id (required).

ledfx_update_configA

Update specific LedFX config sections. May trigger restart for core settings.

Inputs: config (required).

ledfx_update_effectC

Update the configuration of the currently running effect on a virtual

Inputs: virtual_id (required), config (required).

ledfx_update_playlistC

Update an existing LedFX playlist

Inputs: playlist_id (required), name, scene_ids, mode, +1 more.

ledfx_update_sceneC

Update an existing scene in place by ID

Inputs: scene_id (required), name, tags, virtuals, +1 more.

ledfx_update_virtual_configB

Update virtual configuration: transitions, brightness, frequency range, matrix settings, and more.

Inputs: virtual_id (required), transition_mode, transition_time, max_brightness, +6 more.

ledfx_update_virtual_segmentsC

Update the LED segment mapping of a virtual

Inputs: virtual_id (required), segments (required).

ledfx_upsert_color_or_gradientB

Create or update a user-defined color or gradient in LedFX /api/colors.

Inputs: type (required), id (required), value (required).

ledfx_upsert_playlistB

Create or replace a playlist safely. If it exists, updates in place.

Inputs: playlist_id (required), name, scene_ids, mode, +4 more.

ledfx_validate_backupA

Validate a backup JSON structure without restoring it

Inputs: backup (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 83 tools

    Disambiguation4/5

    Most tools have distinct resource-action pairs, but with 83 tools, a few pairs (e.g., apply_global vs apply_global_effect) could cause minor confusion. Descriptions generally clarify, so disambiguation is high but not perfect.

    Naming Consistency5/5

    All tools follow the verb_noun pattern consistently (e.g., activate_scene, list_virtuals, create_backup). No style mixing, making the set predictable and easy to navigate.

    Tool Count2/5

    At 83 tools, the count is very high for an MCP server. While the domain is broad, many operations could be consolidated (e.g., combining similar CRUD tools). This volume risks overwhelming agents.

    Completeness4/5

    The tool surface covers most aspects of LedFX: virtuals, scenes, playlists, effects, devices, integrations, colors, palettes, config, and backups. Minor gaps exist (e.g., no explicit virtual creation tool), but overall it's highly comprehensive.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables control of LIFX smart lights through natural language, including power control, color adjustment, lighting effects, and scene management using the LIFX HTTP API.
      9
      32 npm
      2
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Govee smart devices, including lights, via natural language. Supports turning on/off, changing colors, adjusting brightness, and activating scenes through the Govee API or local network.
      9
      1
      MIT