Permet à un client IA de contrôler le matériel Divoom tel que le PIXOO64, le TimeGate et l'AstroToo pour gérer les cadrans, les animations et les paramètres d'affichage via le réseau local (LAN).
Aussi connu sous DivoomDevelop/mcp-divoom-lan, mcp-divoom-lan
- Étoiles
- 8
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 0.1.1
- Dernier commit
- 27 oct. 2026
- Licence
- MIT
Qu'est-ce que Divoom LAN Watchface MCP ?
Permet à un client IA de contrôler le matériel Divoom tel que le PIXOO64, le TimeGate et l'AstroToo pour gérer les cadrans, les animations et les paramètres d'affichage via le réseau local (LAN).
Résumé généré à partir du README du projet
À propos du MCP server Divoom LAN Watchface
Ce serveur MCP permet aux développeurs et aux passionnés de contrôler les écrans matériels Divoom par le biais du langage naturel. Il fournit une passerelle entre les clients IA comme Claude Desktop ou Cursor et divers appareils connectés en LAN, notamment le PIXOO64, le TimeGate, l'AstroToo et le TimesFrame. En utilisant ce serveur, les utilisateurs peuvent gérer les cadrans, ajuster la luminosité, envoyer du texte ou des animations RGB, et contrôler les paramètres d'alimentation de l'écran directement depuis une interface LLM.
Le serveur fonctionne via une communication par réseau local et nécessite des variables d'environnement spécifiques telles que l'adresse IP et le port de l'appareil. Pour le matériel TimeGate, un LocalToken provenant des paramètres de l'appareil est nécessaire pour les appels authentifiés. Il inclut des outils spécialisés pour différentes versions de matériel, comme le PIXOO64 96 ou le TimeGate 402, garantissant que les commandes telles que la lecture d'animations ou les captures d'écran sont exécutées selon les exigences spécifiques du firmware de l'appareil. Il propose également des outils de création adaptés au modèle pour aider l'IA à suggérer des mises en page et à sélectionner les polices ou les modèles appropriés.
Ce que vous pouvez faire avec
- 1Personnaliser les cadrans matérielsUn client IA peut créer ou mettre à jour des configurations de cadrans locaux sur les appareils AstroToo ou TimesFrame.
- 2Contrôler les animations PIXOO64Les développeurs peuvent ordonner à une IA de lire des GIFs spécifiques ou d'envoyer des animations RGB à un écran PIXOO64.
- 3Gérer les paramètres d'écran TimeGateLes utilisateurs peuvent ajuster à distance la luminosité ou activer/désactiver l'alimentation des cinq écrans indépendants d'un appareil TimeGate.
- 4Automatiser la découverte d'appareilsLe serveur peut identifier le matériel Divoom disponible sur le réseau local afin de déterminer les ports et les modèles compatibles.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Divoom LAN Watchface MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Divoom LAN Watchface MCP dans Claude Code
$ claude mcp add --env 'DIVOOM_DEVICE_HOST=<DIVOOM_DEVICE_HOST>' mcp-divoom-lan -- npx -y mcp-divoom-lanInstaller Divoom LAN Watchface MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-divoom-lan": {
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
],
"env": {
"DIVOOM_DEVICE_HOST": "<DIVOOM_DEVICE_HOST>"
}
}
}
}Installer Divoom LAN Watchface MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"mcp-divoom-lan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
],
"env": {
"DIVOOM_DEVICE_HOST": "<DIVOOM_DEVICE_HOST>"
}
}
}
}Installer Divoom LAN Watchface MCP dans VS Code CLI
$ code --add-mcp '{"name":"mcp-divoom-lan","type":"stdio","command":"npx","args":["-y","mcp-divoom-lan"],"env":{"DIVOOM_DEVICE_HOST":"<DIVOOM_DEVICE_HOST>"}}'Installer Divoom LAN Watchface MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-divoom-lan": {
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
],
"env": {
"DIVOOM_DEVICE_HOST": "<DIVOOM_DEVICE_HOST>"
}
}
}
}Installer Divoom LAN Watchface MCP dans Codex
$ codex mcp add mcp-divoom-lan --env 'DIVOOM_DEVICE_HOST=<DIVOOM_DEVICE_HOST>' -- npx -y mcp-divoom-lanInstaller Divoom LAN Watchface MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-divoom-lan] command = "npx" args = ["-y", "mcp-divoom-lan"] [mcp_servers.mcp-divoom-lan.env] DIVOOM_DEVICE_HOST = "<DIVOOM_DEVICE_HOST>"
Installer Divoom LAN Watchface MCP dans Gemini CLI
$ gemini mcp add -s user -e 'DIVOOM_DEVICE_HOST=<DIVOOM_DEVICE_HOST>' mcp-divoom-lan npx -- -y mcp-divoom-lanInstaller Divoom LAN Watchface MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-divoom-lan": {
"command": "npx",
"args": [
"-y",
"mcp-divoom-lan"
],
"env": {
"DIVOOM_DEVICE_HOST": "<DIVOOM_DEVICE_HOST>"
}
}
}
}Configuration
DIVOOM_DEVICE_HOSTRequisDivoom device LAN IP address
DIVOOM_DEVICE_MODELDIVOOM_DEVICE_PORTDivoom device HTTP port
DIVOOM_TIMEOUT_MSHTTP request timeout in milliseconds
| Nom | Description | Type |
|---|---|---|
| DIVOOM_DEVICE_HOST | Divoom device LAN IP address | Requis |
| DIVOOM_DEVICE_MODEL | — | |
| DIVOOM_DEVICE_PORT | Divoom device HTTP port | |
| DIVOOM_TIMEOUT_MS | HTTP request timeout in milliseconds |
Vérifications automatisées
Exécuté le 13 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)Réussi
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireRéussi
- L'endpoint distant utilise HTTPSNon vérifié
- Les outils destructifs sont étiquetésNon vérifié
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesRéussi
README
Voir sur GitHubmcp-divoom-lan
mcp-divoom-lan is an open-source MCP server for TimesFrame/AstroToo watchfaces and PIXOO64/TimeGate LAN display control. TimesFrame/AstroToo query Device/GetHardwareVersion; PIXOO64/TimeGate use discovery Hardware or explicit hardware profiles. Unknown hardware is rejected. The TimesFrame no-response fallback is retained after checking available discovery data.
PIXOO64 Hardware 90/92 uses 80/post; 96 uses 9000/divoom_api. Its 10 dedicated tools send display elements, text, RGB animations and control commands. Hardware 96 command lists execute sequentially in MCP to match the reference firmware. See the PIXOO64 guide and examples. Device firmware is unchanged.
It works together with the v2 HTML visual editor for modifying watchfaces, switching faces, adjusting brightness, and creating new local watchfaces.
TimeGate Hardware 400 uses 80/post; 402 uses 9000/divoom_api. Its 10 dedicated tools control five independent 128×128 screens and require LocalToken from device settings. Hardware 402 batches run sequentially in MCP. See the TimeGate guide for per-version field, alignment and background differences. Device firmware is unchanged.
v2 visual editor (public):
- GitHub:
https://github.com/DivoomDevelop/divoom-watchface-visual-editor_v2 - Live site:
https://divoomdevelop.github.io/divoom-watchface-visual-editor_v2/
Your local clone path (e.g. D:\divoom-watchface-visual-editor) is machine-specific; use the v2 GitHub / GitHub Pages URLs above in docs and MCP metadata.
Goals
- Expose key capabilities from
Divoom_Watchface_Remote_Customization_Guide_EN.mdas MCP tools - Let MCP-enabled clients (Cursor, Claude Desktop, local LLMs, etc.) drive watchface actions via natural language
- Preserve safety boundaries (read before write, explicit warnings for risky operations, multipart rules)
Default safety policy (important)
- Select the product profile:
Hardware510/511/512 selects TimesFrame; 530 AstroToo; 90/92/96 PIXOO64; 400/402 TimeGate. Explicittarget.hardwareis a caller profile override. Usepixoo64_*ortimegate_*for those products; managed-watchface rules below apply to TimesFrame/AstroToo. - Internal managed slot: users and MCP clients omit
ClockIdfrom create and patch calls. The server injects its managed slot, reads it first, creates it when missing, and updates it when present. - Read before write: the MCP server prechecks its managed slot, writes, and then clients should read back to verify.
- If
GetLocalClockInforeturns an emptyItemList: stop writes; switch to an editable watchface first. - Prefer
watchface_patch_localfor edits. Usewatchface_create_local_clockwhen the user asks to create a watchface or when intentionally replacing the complete managed configuration and backdrop.
Implemented tools (42)
Discovery tool (1):
watchface_list_devices→ returns selectable TimesFrame/AstroToo/PIXOO64/TimeGate targets with product-specific default ports
Device tools (15):
watchface_get_device_info→ hardware identification and LAN capability reportwatchface_get_local→Device/GetLocalClockInfowatchface_patch_local→ managed-slot upsert with no caller-suppliedClockId. Existing configurations useDevice/PatchLocalClockInfo; a missing configuration is created when a backdrop and complete item tables are supplied.watchface_get_fonts_local→Device/GetLocalFontListwatchface_get_store_market_list→Device/GetStoreClockMarketListwatchface_set_clock_select→Channel/SetClockSelectId(TimesFrame queues a paired request inside one serialized MCP operation so a manual selection suppresses the active traditional schedule for the current period; AstroToo sends once)watchface_get_brightness→Sys/GetBrightnesswatchface_set_brightness→Channel/SetBrightnesswatchface_onoff_screen→Channel/OnOffScreen(1=on, 0=off)watchface_replace_dial_bg_file→POST /replace_clock_dial_bgwatchface_upload_file→ AstroToo-onlyPOST /upload_local_asset; returns a temporarylocal://staging reference consumed by a successful create/patch. AstroToo keeps product photo/pixelPOST /uploadseparate. TimesFrame generic/uploadis blocked in local-only MCP mode.watchface_create_local_clock→ managed-slot multipart upsert with no caller-suppliedClockId:/create_local_clockwhen missing and/patch_local_clockwhen already present.watchface_reset_local_then_cloud→Device/ResetLocalClockFromServerwatchface_get_screen_snapshot→Device/GetScreenSnapshot(downloads the returned AstroToo snapshot path; TimesFrame keeps its WebP fallback)watchface_raw_command→ genericPOST /divoom_api
Offline/model-aware authoring tools (6):
watchface_protocol_quick_reference→ key protocol constraints for the modelwatchface_clock_catalog→ product-specific ClockId, Chinese/English names, fonts, disp and item-id semantics; optional native configurationwatchface_disp_catalog→ model-specificdispcatalog and filterswatchface_font_catalog→ model-specific font catalog; with a live AstroToo target it merges local availability into the AstroToo nameswatchface_template_search→ curated TimesFrame or AstroToo watchface templateswatchface_layout_suggest→ model-specific layout hints; AstroToo never receives TimesFrame coordinate statistics
PIXOO64 tools (10): pixoo64_get_device_info, pixoo64_send_animation, pixoo64_send_items, pixoo64_send_text, pixoo64_clear_text, pixoo64_set_brightness, pixoo64_onoff_screen, pixoo64_set_channel, pixoo64_play_gif, and pixoo64_command_list. Read divoom://pixoo64/guide and divoom://pixoo64/example. A direct LAN target can be { "host":"192.168.1.100", "model":"pixoo64", "hardware":90 }; omit port and DIVOOM_DEVICE_PORT to select the version's default.
TimeGate tools (10): timegate_get_device_info, timegate_send_items, timegate_send_text, timegate_clear_text, timegate_set_brightness, timegate_get_brightness, timegate_onoff_screen, timegate_select_clock, timegate_play_gif, and timegate_command_list. Read divoom://timegate/guide and divoom://timegate/example; authenticated calls supply localToken from the actual device settings.
Resources (context for the model)
Product data is stored by directory: resources/timesframe, resources/astrotoo, resources/pixoo64, resources/timegate, and resources/common. resources/products.json records Hardware mappings, per-screen canvas sizes, directories and routes. Runtime loaders never fall back to another product's data.
The original resource URIs retain TimesFrame semantics. AstroToo has separate 480×480 resources:
divoom://products/catalogdivoom://guide/quick-referencedivoom://skill/watchface-customizationdivoom://font/catalogdivoom://font/guidedivoom://disp/catalogdivoom://watchface/schemadivoom://watchface/example-minimaldivoom://guide/ai-watchfacedivoom://templates/curateddivoom://astrotoo/guidedivoom://astrotoo/disp/summarydivoom://astrotoo/disp/catalogdivoom://astrotoo/disp/guide/endivoom://astrotoo/disp/guide/zh-cndivoom://astrotoo/font/catalogdivoom://astrotoo/clocks/catalogdivoom://astrotoo/clocks/configsdivoom://astrotoo/templates/curateddivoom://astrotoo/watchface/example-minimaldivoom://astrotoo/watchface/schema
MCP Bundle (.mcpb)
For MCPB-compatible hosts (e.g. Claude desktop connectors, Smithery stdio releases), build a local bundle:
- Install the packer:
npm install -g @anthropic-ai/mcpb - From this package root:
npm run mcpb:pack - Output:
mcp-divoom-lan.mcpb(gitignored). The staging directorymcpb/staging/is also gitignored.
The bundle includes dist/, resources/, production node_modules, and a manifest.json with user fields for device IP, port, product detection, and timeout.
Quick start
Published npm package:
{
"mcpServers": {
"divoom-lan": {
"command": "npx",
"args": ["-y", "mcp-divoom-lan@latest"],
"env": {
"DIVOOM_DEVICE_HOST": "192.168.1.120",
"DIVOOM_DEVICE_PORT": "9000",
"DIVOOM_DEVICE_MODEL": "auto",
"DIVOOM_TIMEOUT_MS": "45000"
}
}
}
}
DIVOOM_DEVICE_HOST is optional. Leave it unset and include target.host in each tool call when one MCP server controls multiple devices.
Build from source:
cd tools/mcp-divoom-lan # or your clone root for this package
npm install
npm run build
npm start
Development (watch rebuild):
npm run dev
Regenerate AstroToo resources from the simulator and Divoom command server:
$env:DIVOOM_ASTROTOO_SIMULATOR_ROOT='D:\work\divoom_product\timebox\trunck\device\tool_src\lv_sim_visual_studio\LvglAstroTooSimulator'
$env:DIVOOM_ASTROTOO_DEVICE_ID='300400436'
npm run build:astrotoo
The generator calls https://appchina.divoom-gz.com/ + command string with a JSON body. It obtains default IDs from Device/GetClockDefaultList (IsDefault=1), font names from Device/GetFontForAI, and missing configurations from Device/GetClockInfoV3.
Pre-release check (typecheck, build, pack dry-run):
npm run release:check
Documentation
docs/README.md— documentation indexdocs/quick-start.md— minimal setupdocs/mcp-tools.md— complete 42-tool API catalog and model-specific file policydocs/astrotoo-and-multiple-devices.md— hardware detection, multiple targets, and AstroToo local storagedocs/astrotoo-watchface-workflow.md— release-ready AstroToo create, update, switch, and screenshot workflowdocs/adding-products.md— product registry, isolated resource directories, and onboarding checksdocs/tool-examples.md— tool usage examples (includes §5b analog pointer layout)docs/disp-usage.md— choosingdispids (pointer layout131/132/233; net-gallery uniqueness13/125–130/173–175)docs/html-visual-editor.md— using the visual editor with MCPdocs/safety-and-troubleshooting.md— safety and FAQsdocs/reference/— condensed protocol rules (EN/ZH)docs/examples/— sample requests/responses and catalog
Environment variables
DIVOOM_DEVICE_HOST— device LAN IP (e.g.192.168.1.120)DIVOOM_DEVICE_PORT— optional override; omit for PIXOO64 90/92 or TimeGate 400 port80, otherwise9000DIVOOM_DEVICE_MODEL—auto(default),timesframe,astrotoo,pixoo64, ortimegateDIVOOM_DEVICE_HARDWARE— optional default-device profile: PIXOO6490/92/96or TimeGate400/402; omit to use discoveryDIVOOM_TIMEGATE_LOCAL_TOKEN— optional LocalToken from the default TimeGate settings; matched by host, otherwise supplylocalTokenper callDIVOOM_TIMEOUT_MS— request timeout ms, default45000
If DIVOOM_DEVICE_HOST is unset, each tool call must pass target.host. To control several devices, pass a different target on each call. The server serializes a complete operation per host while allowing independent devices to run concurrently.
Example client config (stdio)
Cursor / Claude Desktop
{
"mcpServers": {
"divoom-lan": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/to/tools/mcp-divoom-lan/dist/index.js"
],
"env": {
"DIVOOM_DEVICE_HOST": "192.168.1.120",
"DIVOOM_DEVICE_PORT": "9000",
"DIVOOM_DEVICE_MODEL": "auto",
"DIVOOM_TIMEOUT_MS": "45000"
}
}
}
}
You can also copy client-config.example.json in this directory as a starting point.
Publishing checklist (for maintainers)
- Use a dedicated repo (e.g.
mcp-divoom-lan) with this package at the repo root. - Verify metadata:
LICENSE,SECURITY.md,CONTRIBUTING.md,CHANGELOG.md,RELEASE.mdas applicable. - Run
npm run release:check. - Tag a GitHub release (e.g.
v0.3.0) with screenshots and sample requests if helpful. - Submit listings where appropriate (MCP Registry, Smithery, Glama, MCP.so, and community indexes). For Glama, follow
GLAMA_SUBMISSION_READY.md(includingDockerfileandglama.json). For MCP.so, followMCP_SO_SUBMISSION_READY.md. For the Volcengine MCP catalog, seeVOLCENGINE_SUBMISSION_READY.md(PR: https://github.com/volcengine/mcp-server/pull/398). For an Alibaba Cloud Bailian custom MCP deployed with npx, seeBAILIAN_MCP_SUBMISSION_READY.md. For publishing a Coze HTTP plugin, seeCOZE_SUBMISSION_READY.md. - Minimal demo flow:
watchface_get_local→watchface_patch_local(font size/color) →watchface_replace_dial_bg_file(background).
Files often used at release
Included in this repo (when present): LICENSE, CHANGELOG.md, CONTRIBUTING.md, SECURITY.md, RELEASE.md, optional checklist and directory templates, and .github/workflows/ci.yml.
Should the HTML visual editor ship inside this npm package?
Recommendation: no for the core MCP package — keep MCP lean. Offer the editor as a separate optional project.
- Core:
https://github.com/DivoomDevelop/mcp-divoom-lan - Visual editor v2:
https://github.com/DivoomDevelop/divoom-watchface-visual-editor_v2 - Hosted v2:
https://divoomdevelop.github.io/divoom-watchface-visual-editor_v2/
Benefits:
- Small MCP install suitable for all AI clients
- Non-developers can use the visual UI to understand
ItemList, then let the AI apply patches - Clear split between WYSIWYG editing and automated MCP writes
Alignment with upstream docs
This repo ships standalone docs under docs/, docs/reference/, and docs/examples/. If you maintain full guides elsewhere, keep this tree synced or treat it as the distribution subset.
Questions sur Divoom LAN Watchface MCP
Comment ajouter Divoom LAN Watchface MCP à Claude Code ?
Exécutez claude mcp add --env 'DIVOOM_DEVICE_HOST=<DIVOOM_DEVICE_HOST>' mcp-divoom-lan -- npx -y mcp-divoom-lan dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Divoom LAN Watchface MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Quels appareils matériels ce serveur prend-il en charge ?
Il prend en charge les cadrans et les écrans TimesFrame, AstroToo, PIXOO64 et TimeGate.
Comment puis-je contrôler plusieurs appareils Divoom ?
Si vous ne définissez pas la variable d'environnement DIVOOM_DEVICE_HOST, vous pouvez passer une cible d'hôte différente dans chaque appel d'outil pour contrôler plusieurs appareils.
L'utilisation de ce serveur modifie-t-elle le firmware de mon appareil ?
Non, le firmware de l'appareil reste inchangé lors de l'utilisation de ces outils.
Que faut-il pour contrôler un appareil TimeGate ?
Le matériel TimeGate nécessite un LocalToken obtenu dans les paramètres de l'appareil pour les appels authentifiés.