MCP server for controlling Nanoleaf lights
If you already use Nanoleaf, the nanoleaf mcp server is the piece that lets your assistant work with it directly. MCP server for controlling Nanoleaf lights.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
get_nanoleaf_info — Get detailed device informationset_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 modePrerequisites — The Prerequisites tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: NANOLEAF_AUTH_TOKEN, AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nanoleaf's toolset — get_nanoleaf_info, set_brightness, set_color and 6 more — is a fair guide to whether it matches your workflow. It is maintained by srnetadmin; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_nanoleaf_info | Get detailed device information |
| set_brightness | Adjust brightness (0-100) |
| set_color | Set color using hue (0-360) and saturation (0-100) |
| set_effect | Apply lighting effects |
| get_effects | List all available effects |
| discover_nanoleaf | Discover devices on network |
| connect_to_ip | Connect to specific IP address |
| authorize_nanoleaf | Authorize with device in pairing mode |
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"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": {}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NANOLEAF_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| AUTH_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.