Skip to content
SPECIFICTION
Get listed

DDC-CI Control Bridge

github.com

WindowsmacOSLinuxAPISelf-hosted
Visit github.com
Spec score 7.6 #9 of 24 in Monitor Control Software

What it is

DDC-CI Control Bridge is a free project for controlling compatible monitors through DDC/CI. It can manage brightness, contrast, power, and input, and offers 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, setting brightness from 0 to 100, and rescanning monitors and capabilities. An MQTT client connects it to automation systems. Listed integrations include Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms. The project is available as an npm package or as standalone executables for Windows, Linux, and macOS. MCP can run locally over stdio or provide remote HTTP/SSE access to other machines on a network. Authentication requires the DDC_API_KEY environment variable. The project is MIT licensed and invites contributions through GitHub issues or pull requests. A monitor must support DDC/CI with the feature enabled in its on-screen settings. On Linux, access may require i2c-dev and membership in the i2c group. Some VCP codes are read-only, and supported codes vary by monitor.

Spec sheet

Purpose
The project controls monitor brightness, contrast, power, and input through DDC/CI.Read 4 Oct 2026 · github.com
Intended users
The project describes use by AI agents through MCP and automation platforms through MQTT.Read 4 Oct 2026 · github.com
Deployment
The README describes local stdio setup and remote HTTP/SSE access from other machines on a network.Read 4 Oct 2026 · github.com
Integrations
The README lists Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms.Read 4 Oct 2026 · github.com
Support
The README invites contributions through GitHub issues or pull requests.Read 4 Oct 2026 · github.com
License
The repository identifies the project as MIT licensed.Read 4 Oct 2026 · github.com
Authentication
The server requires a DDC_API_KEY environment variable for authentication.Read 4 Oct 2026 · github.com
Control tools
MCP tools include reading and writing VCP codes, getting and setting brightness from 0 to 100, and rescanning monitors.Read 4 Oct 2026 · github.com
Distribution
It is available as an npm package or as standalone executables for Windows, Linux, and macOS.Read 4 Oct 2026 · github.com
Home Assistant
Supports Home Assistant auto-discovery through the MQTT Discovery Protocol.Read 4 Oct 2026 · github.com
Limitations
The README notes that some monitor VCP codes may be read-only and that supported codes vary by monitor.Read 4 Oct 2026 · github.com
Linux requirement
On Linux, access may require adding the user to the i2c group and enabling i2c-dev.Read 4 Oct 2026 · github.com
MCP server
It includes a Model Context Protocol server with resources and tools for AI or agent integration.Read 4 Oct 2026 · github.com
MCP transports
Supports local stdio setup and remote HTTP/SSE setup.Read 4 Oct 2026 · github.com
Monitor controls
The MCP tools include reading and writing VCP codes, getting and setting brightness, and rescanning monitors and capabilities.Read 4 Oct 2026 · github.com
Monitor requirement
The monitor must support DDC/CI, and DDC/CI must be enabled in its on-screen display settings.Read 4 Oct 2026 · github.com
MQTT client
Its MQTT client connects to MQTT brokers for IoT and automation integrations.Read 4 Oct 2026 · github.com
Other integrations
The README lists openHAB, Node-RED, and Domoticz as supported MQTT integrations.Read 4 Oct 2026 · github.com
Requirements
A monitor must support DDC/CI and have it enabled in its on-screen settings; Linux may require i2c group access.Read 4 Oct 2026 · github.com

Strong points and limits

Strong points

  • Controls brightness, contrast, power, and input.
  • Supports Windows, Linux, and macOS.
  • Offers local stdio and remote HTTP/SSE MCP access.
  • Lists several MQTT automation integrations.

Limits

  • Requires a DDC/CI-compatible monitor with the setting enabled.
  • Linux may require i2c-dev and i2c group access.
  • Some VCP codes are read-only or vary by monitor.
  • Authentication requires a DDC_API_KEY environment variable.

Who it suits

It suits users who want to connect monitor controls to AI agents through MCP or to automation platforms through MQTT. A compatible monitor with DDC/CI enabled is required.

Verdict

DDC-CI Control Bridge connects monitor controls to MCP agents and MQTT automation, with multiple installation and access options. Monitor compatibility and operating-system access requirements are important prerequisites.

Where Specifiction places it

Alternatives to DDC-CI Control BridgeAll alternatives →