FREEDOM251

Freedom251 › Monitor Control Software

DDC-CI Control Bridge

Free plan APILinuxMacSelf-hostedWindows

Visit DDC-CI Control Bridge Alternatives

DDC-CI Control Bridge's own site

What DDC-CI Control Bridge is

DDC-CI Control Bridge is a free tool for controlling compatible monitors through DDC/CI. It can adjust brightness, contrast, power, and input, with monitor controls exposed through a Model Context Protocol (MCP) server and an MQTT client for automation. MCP tools can read and write VCP codes, set brightness from 0 to 100, and rescan monitors and their capabilities. The project lists Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms as integrations. It is distributed as an npm package or 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. The server requires a DDC_API_KEY environment variable for authentication. A monitor must support DDC/CI and have it enabled in its on-screen settings; Linux may also require i2c-dev and i2c group access. Some VCP codes are read-only, and the available codes depend on the monitor.

Who it suits

It suits people who want monitor controls available to AI agents through MCP or to automation platforms through MQTT. It requires a DDC/CI-compatible monitor, and Linux users may need to configure i2c access.

What it does well

  • Controls brightness, contrast, power, and input
  • MCP tools include VCP codes and monitor rescanning
  • MQTT integrations include Home Assistant and Node-RED
  • Available for Windows, Linux, and macOS

What to know first

  • Requires DDC/CI support enabled on the monitor
  • Some VCP codes may be read-only
  • Linux may require i2c-dev and i2c group access

Limits

A monitor must support DDC/CI and have it enabled. Some VCP codes are read-only, and supported codes vary by monitor; Linux may also require i2c-dev and i2c group access.

Getting started

  1. Install the npm package or choose a standalone executable for Windows, Linux, or macOS.
  2. Enable DDC/CI in the monitor’s on-screen settings.
  3. On Linux, enable i2c-dev and arrange i2c group access if required.
  4. Set the DDC_API_KEY environment variable for server authentication.
  5. Configure MCP over local stdio or remote HTTP/SSE, or connect an MQTT platform.

Verdict

DDC-CI Control Bridge combines monitor control with MCP and MQTT integration in a free package. Check monitor compatibility and platform requirements before setting it up.

Questions

Is DDC-CI Control Bridge free?

Yes. It is listed as free, with a free plan.

Which platforms does it support?

Windows, Linux, and macOS are supported. The project is also listed as API and self-hosted.

What integrations are listed?

MQTT integrations include Home Assistant auto-discovery, openHAB, Node-RED, Domoticz, and generic MQTT platforms.

Is it open source?

The repository identifies the project as MIT licensed.

What does it need to control a monitor?

The monitor must support DDC/CI, and DDC/CI must be enabled in its on-screen settings. Linux may require i2c-dev and i2c group access.

Facts from DDC-CI Control Bridge's own pages

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

Where DDC-CI Control Bridge stands on Freedom251

Look at these too