LedFX MCP Server
The LedFX MCP Server lets you control a LedFX LED lighting system through an AI assistant using natural language, exposing 85+ tools for comprehensive LED management.
Device & Virtual Management
List, inspect, activate/deactivate, and configure physical LED devices (WLED, OpenRGB, etc.) and virtual LED strips
Update virtual settings (brightness, transitions, frequency range, matrix layout) and LED segment mappings
Trigger network device discovery
Effect Control
Apply, update, and clear effects on virtuals (rainbow, pulse, wavelength, energy, gradient, scroll, strobe, etc.)
Configure blender effects mixing background, foreground, and mask layers
Manage effect history and trigger fallback effects
Bulk-apply effects or global config to multiple virtuals at once
Preset Management
Browse, apply, save, and delete effect presets per virtual
Scene Management
List, activate, create, update, rename, and delete scenes
Set a startup scene that auto-activates on launch
Create scenes from natural language descriptions (AI-powered)
Playlist Management
Create, update, delete, start, and stop playlists of scene sequences
Add, remove, and reorder scenes within playlists
Color & Palette Management
List, create, update, and delete user-defined colors and gradients
Manage named palettes stored as user gradients
Audio Management
List available audio input devices and set the active device for audio-reactive effects
Global Controls
Get/set global brightness, toggle global pause, and clear all active effects across all virtuals
AI-Powered Features
Get effect recommendations based on mood or description
Get explanations of any LedFX feature or concept
Configuration & Backup
Get, update, import, and reset LedFX configuration
Create, restore, and validate full configuration backups (with selective restore options)
Integrations
List, create, toggle, and delete integrations (e.g., QLC+, Spotify)
Manage QLC+ event mappings
System
Get server info (version, features)
Shutdown or restart LedFX
Send custom notifications to the LedFX frontend UI
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LedFX MCP Server apply a rainbow effect to the living room virtual"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
API Corrections Applied: Effects are correctly applied to virtuals (not devices), matching current LedFX API behavior
Comprehensive Testing: 34 tests covering unit and E2E scenarios - all passing
CI/CD Pipeline: GitHub Actions workflow with lint, build, test, and coverage jobs
Production Ready: Fully documented with installation guide, usage examples, and architecture docs
Documentation
API Specification - Complete LedFX API reference
Test Specification - Comprehensive test plans
Implementation Notes - Design decisions and technical notes
References - LedFX resources and links
Installation Guide - Step-by-step setup instructions
Usage Guide - How to use all features
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:latestUsing pip:
pip install ledfx
ledfx --host 0.0.0.0 --port 8888See 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
nodewithdist/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 |
| Get LedFX server information (version, features) |
| List all physical LED devices |
| Get details about a specific device |
| List all virtual LED strips (includes global paused state) |
| Get details about a specific virtual |
| Activate/deactivate a virtual |
| Update virtual config (transitions, brightness, frequency range, matrix) |
| Trigger network device discovery |
| Check if all virtuals are globally paused |
| Toggle global pause on all virtuals |
| Get global brightness value (0-1) |
| Set global brightness for all virtuals |
| Set scene to activate on LedFX startup |
| Send notification to LedFX frontend UI |
| Get current Now Playing state (track metadata, artwork) and config |
| Update Now Playing config (gradient / track_text / album_art sections) |
Effect Control (CORRECTED - uses virtuals)
Tool | Description |
| Apply an effect to a virtual (not device) |
| Update effect configuration |
| Remove effects from a virtual |
| Get schemas for all effect types |
Scene Management
Tool | Description |
| List all available scenes |
| Activate a pre-configured scene |
| Create new scene from current config |
| Delete a saved scene |
| AI-powered scene creation from natural language |
Palette Management (LedFX /api/colors)
Tool | Description |
| List all palettes stored as user gradients |
| Create/update a palette (stored as user gradient) |
| Get palette by name |
| Delete a palette by name |
Playlist Management
Tool | Description |
| List all playlists |
| Create scene sequence playlist |
| Get specific playlist |
| Delete a playlist |
Color Management (LedFX /api/colors)
Tool | Description |
| List all colors and gradients from LedFX |
| Get a specific color or gradient by ID |
| Create/update a user color or gradient |
| Delete a user color or gradient |
| Delete all user-defined gradients (includes palettes) |
AI Features
Tool | Description |
| Get effect recommendations based on mood/description |
| Get detailed explanation of any LedFX feature |
| List all explainable features |
| List all effect types with descriptions |
Preset Management
Tool | Description |
| Get presets for a virtual's effect |
| Apply a preset to a virtual |
| Save current effect as a user preset |
| Delete a preset for a virtual |
Audio Management
Tool | Description |
| List audio input devices |
| 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:fixProject 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 fileDocumentation
Comprehensive documentation is available in the docs/ directory:
API Specification
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
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
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
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:
MCP Server Layer (
index.ts): Handles MCP protocol communicationTools Layer (
tools.ts): Defines available tools and routes requestsClient 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_HOSTandLEDFX_PORTenvironment variables
Tools not appearing in Claude
Restart Claude Desktop after configuration changes
Verify the path to
dist/index.jsis absoluteCheck Claude Desktop logs for errors
Support
For issues and questions:
Available Tools
83 toolsledfx_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
Scored across 83 tools
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.
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.
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.
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
Related MCP Connectors
Control your Tesla from your AI assistant - climate, charging, access, and security.
Control your existing Philips lights, Sonos speakers, Roborock vacuums and other supported devices through Port OS cloud. Give ChatGPT, Claude and other MCP-compatible assistants access to the devices you connect. Turn off the living room lights, play music on your speakers, adjust the thermostat, run a vacuum in a room, check a camera snapshot or find a connected tracker. Available actions depend on your linked provider accounts and each deviceās supported capabilities. Port OS runs in the cloud; no local server is required. You choose the account, device and capability permissions each assistant receives. Device operations require user OAuth; public tool discovery does not grant device access. Port OS is in alpha. Setup: https://portoperatingsystem.com/docs/getting-started/ Support: https://portoperatingsystem.com/contact/
Manage digital signage screens, playlists and media from your AI assistant.
Home energy for AI assistants: live Power flow, Energy history, solar forecast, and device control.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables control of LIFX smart lights through natural language, including power control, color adjustment, lighting effects, and scene management using the LIFX HTTP API.932 npm2ISC
- AlicenseAqualityDmaintenanceEnables 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.91MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control Philips Hue smart lighting systems using natural language, supporting light control, group management, scenes, and presets.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to control Home Assistant via natural language, including device control, automation management, and system monitoring.MIT