Nanoleaf MCP Server
A server for controlling Nanoleaf smart lights using the Model Context Protocol.
Nanoleaf MCP Server
A Model Context Protocol (MCP) server for controlling Nanoleaf smart lights. This server provides tools to control your Nanoleaf devices through Warp terminal or any MCP-compatible client.
Features
- 🔍 Auto-discovery of Nanoleaf devices on your network
- 🔗 Direct IP connection for specific device targeting
- 🔐 Authorization support for secure device pairing
- 💡 Full control of lights, brightness, colors, and effects
- 🐳 Dockerized for easy deployment
- 🖥️ Warp terminal integration
- 🔒 Security-audited dependencies with regular vulnerability checks
Available Tools
get_nanoleaf_info- Get detailed device informationturn_on_nanoleaf/turn_off_nanoleaf- Control power stateset_brightness- Adjust brightness (0-100)set_color- Set color using hue (0-360) and saturation (0-100)set_effect- Apply lighting effectsget_effects- List all available effectsdiscover_nanoleaf- Discover devices on networkconnect_to_ip- Connect to specific IP addressauthorize_nanoleaf- Authorize with device in pairing mode
Quick Setup Guide
Automated Setup (Recommended)
For the easiest setup experience, use the included setup script:
./setup.sh
This script will:
- Build the Docker image
- Scan for Nanoleaf devices on your network
- Help you get the authorization token
- Create all configuration files
- Test the setup
- Generate your Warp configuration
Manual Setup
Prerequisites
- Docker installed on your system
- Nanoleaf device(s) on your network
- Warp terminal (optional, for MCP integration)
Step 1: Clone and Build
git clone <repository-url>
cd nanoleaf-mcp-server
docker build -t nanoleaf-mcp-server-nanoleaf-mcp-server .
Step 2: Find Your Nanoleaf Device
Option A: Auto-discovery
docker run --rm -i --network=host nanoleaf-mcp-server echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "discover_nanoleaf", "arguments": {}}}'
Option B: Manual IP scan
# Scan your network for devices responding on Nanoleaf port
nmap -p 16021 192.168.1.0/24
Option C: Check router admin panel for connected devices
Step 3: Get Authorization Token
-
Put your Nanoleaf device in pairing mode:
- Hold the power button on your Nanoleaf device for 5-7 seconds
- Look for pairing indicator (usually a flashing light)
-
Get the auth token immediately (within 30 seconds):
# Replace 192.168.1.100 with your device's IP curl -X POST http://192.168.1.100:16021/api/v1/newYou should get a response like:
{"auth_token":"YourAuthTokenHere123456789"}
Step 4: Configure Environment
Create a .env file in the project directory:
NANOLEAF_IP=192.168.1.100
NANOLEAF_AUTH_TOKEN=YourAuthTokenHere123456789
NANOLEAF_PORT=16021
NANOLEAF_PROTOCOL=http
Step 5: Test Your Setup
# Test with environment variables
docker run --rm -i --network=host --env-file .env nanoleaf-mcp-server echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "get_nanoleaf_info", "arguments": {}}}'
If successful, you'll see detailed information about your Nanoleaf device!
Step 6: Run Examples (Optional)
Test all functionality with the example script:
./examples.sh
This will demonstrate all available features including turning lights on/off, changing colors, and applying effects.
Working Example
Here's a complete working example with real values (replace with your own):
- Device discovered at:
<DEVICE_IP>:16021 - Auth token obtained:
<AUTH_TOKEN> - Warp configuration:
{
"mcpServers": {
"nanoleaf": {
"command": "docker",
"args": [
"run", "--rm", "-i", "--network=host",
"-e", "NANOLEAF_IP=<DEVICE_IP>",
"-e", "NANOLEAF_AUTH_TOKEN=<AUTH_TOKEN>",
"-e", "NANOLEAF_PORT=16021",
"-e", "NANOLEAF_PROTOCOL=http",
"nanoleaf-mcp-server-nanoleaf-mcp-server"
],
"env": {}
}
}
}
- Test command:
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "set_effect", "arguments": {"effect": "Cyberpunk 2077"}}}' | docker run --rm -i --network=host -e NANOLEAF_IP=<DEVICE_IP> -e NANOLEAF_AUTH_TOKEN=<AUTH_TOKEN> nanoleaf-mcp-server-nanoleaf-mcp-server
Warp Terminal Integration
Add to Warp MCP Configuration
Add this to your Warp MCP servers configuration (replace the values with your actual device IP and auth token):
{
"mcpServers": {
"nanoleaf": {
"command": "docker",
"args": [
"run", "--rm", "-i", "--network=host",
"-e", "NANOLEAF_IP=192.168.1.100",
"-e", "NANOLEAF_AUTH_TOKEN=YourAuthTokenHere123456789",
"-e", "NANOLEAF_PORT=16021",
"-e", "NANOLEAF_PROTOCOL=http",
"nanoleaf-mcp-server-nanoleaf-mcp-server"
],
"env": {}
}
}
}
Important:
- Replace
192.168.1.100with your Nanoleaf device's IP address - Replace
YourAuthTokenHere123456789with your actual auth token - Make sure you've built the Docker image with tag
nanoleaf-mcp-server-nanoleaf-mcp-server
Alternative Configuration (if path issues occur)
If you encounter path-related issues, you can also use this alternative approach:
{
"mcpServers": {
"nanoleaf": {
"command": "bash",
"args": ["-c", "cd /path/to/nanoleaf-mcp-server && docker run --rm -i --network=host --env-file .env nanoleaf-mcp-server-nanoleaf-mcp-server"],
"env": {}
}
}
}
Using in Warp
Once configured, you can use the Nanoleaf tools directly in Warp:
- Ask to turn lights on/off
- Change brightness and colors
- Apply cool effects like "Northern Lights" or "Cyberpunk"
- Get device information
Manual Usage Examples
Turn lights on/off
# Turn on
curl -X PUT http://your-ip:16021/api/v1/your-token/state \
-H "Content-Type: application/json" \
-d '{"on":{"value":true}}'
# Turn off
curl -X PUT http://your-ip:16021/api/v1/your-token/state \
-H "Content-Type: application/json" \
-d '{"on":{"value":false}}'
Set brightness
curl -X PUT http://your-ip:16021/api/v1/your-token/state \
-H "Content-Type: application/json" \
-d '{"brightness":{"value":50}}'
Apply an effect
curl -X PUT http://your-ip:16021/api/v1/your-token/effects \
-H "Content-Type: application/json" \
-d '{"select":"Northern Lights"}'
Troubleshooting
Device Not Found
- Ensure device is on the same network
- Check firewall settings
- Try manual IP scanning:
nmap -p 16021 192.168.1.0/24
Authorization Failed
- Device must be in pairing mode (hold power button 5-7 seconds)
- Pairing mode only lasts ~30 seconds
- Make sure no other devices are already controlling it
Connection Issues
- Verify IP address is correct
- Check if device uses HTTPS (some newer models)
- Ensure Docker has network access (
--network=host)
Environment Variables Not Working
- Check
.envfile exists and has correct values - Verify Docker command includes
--env-file .env - Make sure file paths are absolute in Warp config
Warp Terminal Issues
"The system cannot find the path specified" error
- Use the direct environment variable configuration instead of
--env-file - Make sure your Docker image tag matches exactly:
nanoleaf-mcp-server-nanoleaf-mcp-server - Try the alternative bash configuration if path issues persist
MCP server not responding in Warp
- Verify the Docker image is built with the correct tag
- Check that your IP address and auth token are correct in the configuration
- Test the Docker command manually first:
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "get_nanoleaf_info", "arguments": {}}}' | docker run --rm -i --network=host -e NANOLEAF_IP=your-ip -e NANOLEAF_AUTH_TOKEN=your-token nanoleaf-mcp-server-nanoleaf-mcp-server
"MCP server exited" in logs
- This usually indicates a configuration issue
- Check that all environment variables are properly set
- Ensure the Docker image exists:
docker images | grep nanoleaf
Device Compatibility
Tested with:
- Nanoleaf Canvas
- Nanoleaf Light Panels
- Nanoleaf Hexagons
Should work with most Nanoleaf devices that support the v1 API.
Documentation
- Dependency Audit Report - Detailed security audit and dependency update information
- Setup Scripts - Automated setup and testing scripts included
- Docker Configuration - Containerized deployment for easy management
Contributing
Feel free to submit issues, feature requests, or pull requests!
License
MIT License - see LICENSE file for details.
संबंधित सर्वर
MCP HUB
The Ultimate Control Plane for MCP Unlock the full power of Model Context Protocol with zero friction. One-Click GPT Integration: Bridge the gap between MCP servers and ChatGPT/LLMs instantly. No more manual config hunting. Pro-Level Orchestration: Manage, monitor, and toggle multiple MCP tools from a single, intuitive dashboard. Secure by Design: Built-in support for complex auth flows and 2FA, making enterprise-grade tool integration seamless. Streamlined Debugging: Test queries and inspect tool responses in real-time without leaving the hub. Stop wrestling with JSON configs. Start building agentic workflows that actually work.
SyncGTM Enrichment MCP
MCP server for B2B data enrichment - enrich companies, find contacts, and detect buying signals from Claude, Cursor, or any AI tool. 75+ actions across 20+ data providers.
MCP Dev Brasil
37 MCP servers for agentic commerce — Stripe ACP, x402, AP2, Google UCP, plus 14 Brazilian payment rails. ~480 tools.
Polymarket MCP
Self-hosted MCP server for AI agent trading on Polymarket. 42 tools for market discovery, order placement, wallet intelligence, copy trading, and reward discovery.
Tokyo WBGT MCP Server
Provides real-time and forecast WBGT (Heat Index) data for Tokyo from Japan's Ministry of the Environment.
sbb-mcp
Swiss Federal Railways (SBB/CFF/FFS) MCP server — real-time train schedules, ticket prices with Half-Fare/GA support, and direct purchase links via official SBB SMAPI
FHIR MCP Server
FHIR MCP Server – helping you expose any FHIR Server or API as a MCP Server.
UFO MCP Server
Control a Dynatrace UFO device on your local network using MCP-compatible clients.
MCP-Airflow-API
MCP-Airflow-API is an MCP server that leverages the Model Context Protocol (MCP) to transform Apache Airflow REST API operations into natural language tools. This project hides the complexity of API structures and enables intuitive management of Airflow clusters through natural language commands.
PRH Finnish Company Registry MCP Server
MCP server for PRH (Finnish Patent and Registration Office). Free public API — look up any Finnish company by name, business ID, location, or industry. No auth required.