DDC-CI Control Bridge
DDC-CI Control Bridge is a free project for controlling compatible monitors through DDC/CI.
What DDC-CI Control Bridge is
DDC-CI Control Bridge is a free project for controlling compatible monitors through DDC/CI. It can manage brightness, contrast, power, and input, with command-line or API access. Its Model Context Protocol server provides resources and tools for AI or agent integration, including reading and writing VCP codes, adjusting brightness from 0 to 100, and rescanning monitors and capabilities. An MQTT client connects to automation platforms; listed integrations include Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT systems. The project is available as an npm package or standalone executables for Windows, Linux, and macOS. MCP can use local stdio or remote HTTP/SSE access from other machines on a network. Authentication requires a DDC_API_KEY environment variable. A monitor must support DDC/CI and have it enabled in its on-screen settings. Linux may require i2c-dev and i2c group access. Some monitor VCP codes may be read-only, and supported codes vary by monitor.
Good
- Controls brightness, contrast, power, and input.
- Supports MCP and MQTT integrations.
- Available for Windows, Linux, and macOS.
- Free and MIT licensed.
Watch out
- Requires a monitor with DDC/CI enabled.
- Linux may require i2c-dev and i2c group access.
- Some VCP codes may be read-only.
Who it suits
DDC-CI Control Bridge suits users connecting compatible monitors to AI agents through MCP or automation platforms through MQTT. It is aimed at people comfortable with monitor requirements and setup across Windows, Linux, or macOS.
Verdict
DDC-CI Control Bridge offers monitor controls alongside MCP and MQTT integration options. Confirm that your monitor supports enabled DDC/CI and account for the Linux access requirements if applicable.
The facts
Each one read from DDC-CI Control Bridge's own pages, with the date it was checked.
What it does
- Authentication
- The server requires a DDC_API_KEY environment variable for authentication.checked 4 Oct 2026
- Control tools
- MCP tools include reading and writing VCP codes, getting and setting brightness from 0 to 100, and rescanning monitors.checked 4 Oct 2026
- Deployment
- The README describes local stdio setup and remote HTTP/SSE access from other machines on a network.checked 4 Oct 2026
- Distribution
- It is available as an npm package or as standalone executables for Windows, Linux, and macOS.checked 4 Oct 2026
- Home Assistant
- Supports Home Assistant auto-discovery through the MQTT Discovery Protocol.checked 4 Oct 2026
- Integrations
- The README lists Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms.checked 4 Oct 2026
- Intended users
- The project describes use by AI agents through MCP and automation platforms through MQTT.checked 4 Oct 2026
- License
- The repository identifies the project as MIT licensed.checked 4 Oct 2026
- Limitations
- The README notes that some monitor VCP codes may be read-only and that supported codes vary by monitor.checked 4 Oct 2026
- MCP server
- It includes a Model Context Protocol server with resources and tools for AI or agent integration.checked 4 Oct 2026
- MCP transports
- Supports local stdio setup and remote HTTP/SSE setup.checked 4 Oct 2026
- Monitor controls
- The MCP tools include reading and writing VCP codes, getting and setting brightness, and rescanning monitors and capabilities.checked 4 Oct 2026
- Monitor requirement
- The monitor must support DDC/CI, and DDC/CI must be enabled in its on-screen display settings.checked 4 Oct 2026
- MQTT client
- Its MQTT client connects to MQTT brokers for IoT and automation integrations.checked 4 Oct 2026
- Other integrations
- The README lists openHAB, Node-RED, and Domoticz as supported MQTT integrations.checked 4 Oct 2026
- Purpose
- The project controls monitor brightness, contrast, power, and input through DDC/CI.checked 4 Oct 2026
- Requirements
- A monitor must support DDC/CI and have it enabled in its on-screen settings; Linux may require i2c group access.checked 4 Oct 2026
- Support
- The README invites contributions through GitHub issues or pull requests.checked 4 Oct 2026
Where it runs
- Linux requirement
- On Linux, access may require adding the user to the i2c group and enabling i2c-dev.checked 4 Oct 2026
Alternatives to DDC-CI Control Bridge
- 1
ddcutil
Free planAPILinuxSelf-hosted6.6Free plan - 2
ClickMonitorDDC
Free planWindows6.5Free plan - 3
Lunar
Free planmacOS6.5$23 one-time - 4
DisplayBuddy
macOSWindows6.3$24.99 one-time - 5
Monitor Switch
Free planWebAPILinuxSelf-hosted6.3Free plan - 6
AOC G-Menu
Free planWindows6.2Free plan