Create and preview pixel art, text, scenes and animations, then send them to a Divoom Pixoo display on your local network.
Pixoo MCP connects an assistant to a Divoom Pixoo LED display. It can render text, images, layered scenes and animations, then push the finished frames to a reachable device. Rendering happens on the host computer.
Use a rendering tool with push: false to inspect the output without changing a display. The returned preview and layout details help identify clipped text or a design that does not fit the panel. The design-brief tool supplies guidance and device context for the next step.
The current README requires Bun 1.4.0 or later, or Node.js 24 or later. Set PIXOO_IP to the device’s LAN address in the publisher configuration. Device discovery uses Divoom’s cloud discovery service and therefore needs internet access.
Read the device state before pushing. Brightness, screen power and the selected channel can explain why a successful render is not visible. Some longer animations require the device to download a generated GIF from the host, so that network path must also work.
The HTML renderer needs the documented headless browser and can be disabled with PIXOO_HTML_ENABLED=false. Its availability depends on the local setup; it should not be assumed from the package name alone.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| pixoo_display_text | Render styled text with themes, gradients, shadows, and auto-fit, static or animated, and push it |
| pixoo_compose_scene | Compose layered scenes of text, icons, widgets, shapes, bitmaps, images, and sprites, static or animated |
| pixoo_push_image | Resize a local or https image to the LED grid and push it, an animated GIF or WebP as an animation |
| pixoo_render_html | Render an HTML page (CSS, SVG, Canvas, WebGL) in a headless browser at the panel size, still or animated frame by frame on a virtual clock, and push it |
| pixoo_overlay_text | Set or clear a device-rendered scrolling text overlay |
| pixoo_control_device | Read or change brightness, screen state, channel, or clock face |
| pixoo_discover_devices | Find Pixoo devices and their LAN IPs through Divoom's cloud discovery |
| pixoo_design_brief | Craft guidance for a design topic, with live device state and pre-filled next calls |
{
"mcpServers": {
"pixoo-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": [
"@cyanheads/pixoo-mcp-server@latest"
],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"PIXOO_IP": "192.168.1.50"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Bun 1.4.0 or later, or Node.js 24 or later. Device pushes need a reachable Divoom Pixoo on the local network. The optional HTML renderer needs the publisher’s documented headless browser.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT_TYPE | Selects the configured transport; the documented local example uses stdio. | Optional |
| MCP_LOG_LEVEL | Controls logging verbosity. | Optional |
| PIXOO_IP | LAN address for device pushes. Preview-only rendering and discovery can work without it. | Optional |
Enables natural language interaction with Home Assistant entities using the Model Context Protocol.
Integrates with Home Assistant to provide smart home control capabilities via Model Context Protocol (MCP).
A Model Context Protocol (MCP) server that enables AI agents to interact with the 1NCE IoT connectivity management platform through natural language.
Agriculture Robotics tools for AI agents. Capabilities: robot safety check, spray plan calcu...
Amazon Alexa for Claude — Echo devices, announcements, routines, smart home, lists
Connect Claude, Cursor, Codex, and other AI tools to your robotics mission data.