get_nanoleaf_infoLABSCO SUMMARY
Lights that answer a sentence.
Discovery and pairing are part of the tool surface rather than a separate setup ritual, so the same conversation that finds the device is the one that dims it.
What it is
An MCP server for Nanoleaf smart lights. It discovers devices on the network or connects to a known IP, completes the pairing handshake while the device is in pairing mode, then controls power, brightness, colour and effects.
What you get
- Devices discovered on the network, or reached at a known IP
- Pairing completed while the device is in pairing mode
- Device information read back
- Power switched on
- Brightness set, on a 0 to 100 scale
- Colour set by hue, and by saturation on a 0 to 100 scale
- The effects on the device listed, and one of them applied
Requirements
Docker, and a Nanoleaf device on the same network. Pairing is one-time: hold the device's power button down until it enters pairing mode, then call the authorize tool to get the token. The included setup.sh does the build, the network scan, the token and the config in one pass.
Setup effort
One command plus a key — docker build -t nanoleaf-mcp-server-nanoleaf-mcp-server ., then supply credentials
USE CASES
01
Setting the room for a call
Brightness and colour are two calls, both with numeric ranges rather than named presets.
02
Starting a scene without hunting for the app
List what is on the device, then apply the one you want by name.
03
Getting a new device working
Scan the network for it, then pair while it is in pairing mode.
04
Reaching a device whose IP you already reserved
Skip discovery, connect to the address, and read the device info back to confirm.
05
Turning everything on when you sit down
Power on and set the brightness in one exchange.
10 tools
Listed in project docs. Your client may show a different list.
turn_on_nanoleafturn_off_nanoleafset_brightnessset_colorset_effectget_effectsdiscover_nanoleafconnect_to_ipauthorize_nanoleafBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- docker on PATH
- NANOLEAF_AUTH_TOKEN in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
docker build -t nanoleaf-mcp-server-nanoleaf-mcp-server .MCP Clients
Warp — Docker
WARP — DOCKER · JSON
{
"mcpServers": {
"nanoleaf": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--network=host",
"-e",
"NANOLEAF_IP=192.168.1.100",
"-e",
"NANOLEAF_AUTH_TOKEN=<YOUR_NANOLEAF_AUTH_TOKEN>",
"-e",
"NANOLEAF_PORT=16021",
"-e",
"NANOLEAF_PROTOCOL=http",
"nanoleaf-mcp-server-nanoleaf-mcp-server"
],
"env": {}
}
}
}Warp — bash
WARP — BASH · JSON
{
"mcpServers": {
"nanoleaf": {
"command": "bash",
"args": [
"-c",
"cd <YOUR_PATH_TO_NANOLEAF_MCP_SERVER> && docker run --rm -i --network=host --env-file .env nanoleaf-mcp-server-nanoleaf-mcp-server"
],
"env": {}
}
}
}
