Divoom LAN Watchface
Let your coding agent push watchfaces and LAN commands to a Divoom pixel display on your local network without unsafe blind writes.
Overview
Divoom LAN Watchface is an MCP server for the Build phase that exposes Divoom LAN watchface APIs to AI agents with read-before-write safety.
What is this MCP server?
- Stdio MCP server (mcp-divoom-lan 0.1.1) over npx with DIVOOM_DEVICE_HOST required
- Read-before-write safety for LAN watchface APIs
- Configurable DIVOOM_DEVICE_PORT (default 9000) and DIVOOM_TIMEOUT_MS (default 45000)
- README links Divoom V2 editor for designing faces before upload
- Server schema version 0.1.1
- Default HTTP port 9000 and timeout 45000 ms per server.json
Community signal: 1 GitHub stars.
What problem does it solve?
You want your agent to update a Divoom display on the LAN but fear overwriting device state without reading current settings first.
Who is it for?
Indie builders with a Divoom on the same network who want MCP-driven watchface tweaks and scripted desk automation.
Skip if: Teams without Divoom hardware, cloud-only deployments, or anyone who needs official cloud OAuth instead of LAN HTTP.
What do I get? / Deliverables
After you register the server with your device IP, the agent can safely inspect and apply watchface changes through MCP tools aligned with Divoom’s LAN API.
- Agent-callable LAN watchface read/write flows with safety semantics
- Configured MCP stdio bridge to the Divoom HTTP port
Recommended MCP Servers
Journey fit
Hardware and LAN API wiring sits in the build phase when you integrate side projects, desk gadgets, or IoT demos with your agent workflow. integrations is the canonical shelf because the server exposes device HTTP APIs over MCP rather than UI or backend app logic.
How it compares
LAN hardware MCP integration, not a watchface design studio or generic image pipeline.
Common Questions / FAQ
Who is Divoom LAN Watchface for?
Solo developers and hobbyists who run MCP-enabled agents and own a Divoom device reachable on their local network.
When should I use Divoom LAN Watchface?
Use it during build when you are wiring agent workflows to physical displays and need read-before-write LAN watchface operations.
How do I add Divoom LAN Watchface to my agent?
Add the stdio MCP entry (npx mcp-divoom-lan), set DIVOOM_DEVICE_HOST to your device IP, optionally port and timeout, then restart your MCP host.