Thanks for contributing to mcp-divoom-lan.
Contributions are welcome for:
- MCP tool quality and reliability
- protocol safety constraints
- docs and examples
- compatibility with MCP clients
npm install
npm run check
npm run build- Keep changes focused and reviewable.
- Update
README.mdwhen behavior or config changes. - Add/update
CHANGELOG.mdunderUnreleasedor next target version. - Preserve wire-level compatibility with Divoom LAN API:
- request
ReturnCodemust stay0 - multipart must include
filename="..."and per-partContent-Length
- request
- Never commit secrets, private IP inventories, or production credentials.
Before opening PR:
npm run checknpm run buildnpm pack --dry-run
For endpoint changes, include at least one real or simulated request/response example in the PR description.
Use concise, purpose-oriented messages, for example:
feat: add market list tool wrapperfix: enforce multipart filename headerdocs: clarify reset command risk