DDC-CI Control Bridge
github.com
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What DDC-CI Control Bridge is
DDC-CI Control Bridge is free software for controlling compatible monitors through DDC/CI. It can read and write VCP codes, adjust brightness from 0 to 100, manage contrast and power, switch inputs, and rescan monitors and their capabilities. An MCP server exposes resources and tools for AI agents, with local stdio operation or remote HTTP/SSE access on a network. An MQTT client connects monitor controls to brokers and automation systems, including Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms. You can use the project as an npm package or standalone executable on Windows, Linux, or macOS. The server requires the DDC_API_KEY environment variable. A monitor must support DDC/CI with that option enabled in its on-screen settings; Linux systems may also need i2c-dev and i2c-group access. Some VCP codes are read-only, and available controls differ between monitors. The repository is MIT licensed.
Who it suits
It suits people who want programmatic monitor control, AI-agent integration, or MQTT-based automation on Windows, Linux, or macOS. It is intended for compatible DDC/CI monitors and users comfortable with local or network server setup.
Good to know, and what to watch
- Free plan with no listed charge
- MCP tools support monitor control and rescanning
- MQTT integrations include Home Assistant and Node-RED
- Available as npm package or standalone executables
- Supports local and remote MCP transports
- Requires a DDC/CI-compatible monitor
- Linux may require i2c-dev and i2c-group access
- Some VCP codes are read-only
- Supported controls vary by monitor
The verdict
DDC-CI Control Bridge combines monitor controls with MCP and MQTT connectivity. Check your monitor’s DDC/CI support and Linux permissions before deployment.
What the maker publishes
- Authentication
- The server requires a DDC_API_KEY environment variable for authentication. source
- Control tools
- MCP tools include reading and writing VCP codes, getting and setting brightness from 0 to 100, and rescanning monitors. source
- Deployment
- The README describes local stdio setup and remote HTTP/SSE access from other machines on a network. source
- Distribution
- It is available as an npm package or as standalone executables for Windows, Linux, and macOS. source
- Home Assistant
- Supports Home Assistant auto-discovery through the MQTT Discovery Protocol. source
- Integrations
- The README lists Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms. source
- Intended users
- The project describes use by AI agents through MCP and automation platforms through MQTT. source
- License
- The repository identifies the project as MIT licensed. source
- Limitations
- The README notes that some monitor VCP codes may be read-only and that supported codes vary by monitor. source
- Linux requirement
- On Linux, access may require adding the user to the i2c group and enabling i2c-dev. source
- MCP server
- It includes a Model Context Protocol server with resources and tools for AI or agent integration. source
- MCP transports
- Supports local stdio setup and remote HTTP/SSE setup. source
- Monitor controls
- The MCP tools include reading and writing VCP codes, getting and setting brightness, and rescanning monitors and capabilities. source
- Monitor requirement
- The monitor must support DDC/CI, and DDC/CI must be enabled in its on-screen display settings. source
- MQTT client
- Its MQTT client connects to MQTT brokers for IoT and automation integrations. source
- Other integrations
- The README lists openHAB, Node-RED, and Domoticz as supported MQTT integrations. source
- Purpose
- The project controls monitor brightness, contrast, power, and input through DDC/CI. source
- Requirements
- A monitor must support DDC/CI and have it enabled in its on-screen settings; Linux may require i2c group access. source
- Support
- The README invites contributions through GitHub issues or pull requests. source
Checked against the maker's pages on 4 Oct 2026.