DDC/CI Bridge

You can control and automate DDC/CI monitor settings from a single MCP server that talks to your monitors via DDC/CI, while also exposing resources and tools for AI agents and integrating with MQTT brokers for home automation. This bridge centralizes monitor control, makes it easy to read and write VCP values, and allows remote or local access to your monitors from various MCP clients and automation platforms.

How to use

You will run the MCP server on a machine with access to your monitors. You can connect to it locally using stdio-based MCP clients or remotely over HTTP from other devices on your network. The server exposes monitor data as MCP resources and provides actions (tools) to read and write VCP codes, as well as convenience functions like getting and setting brightness.

How to install

# Option 1: NPM Package (Global)
npm install -g ddc-ci-control-bridge
ddc-ci-bridge

# Option 2: NPX (No Install)
npx ddc-ci-control-bridge

# Option 3: Standalone Executable
# Windows
# Download ddc-ci-bridge-win.exe from GitHub Releases
# Then run after setting API key

# Linux
# Download ddc-ci-bridge-linux, make executable, then run

# macOS
# Download ddc-ci-bridge-macos, make executable, then run

Additional installation and setup notes

If you choose the standalone executable option, you must provide an API key via the DDC_API_KEY environment variable, or the executable will exit. You can also configure multiple environment variables for MQTT and transport settings as needed.

Configuration and remote access

You can enable remote access by running the MCP server on the monitor-connected machine and configuring clients to connect over HTTP. The server will announce its address and port, for example, a typical setup uses port 8000 with an SSE transport. Use the API key you configured to authorize remote clients.

MQTT integration and automation

The server can act as an MQTT client and publish monitor state and VCP changes to any MQTT broker. You can enable MQTT to integrate with automation platforms like Home Assistant, openHAB, Node-RED, and others. Use the MQTT topics to subscribe to or publish values for brightness, contrast, VCP codes, and bridge status.

Tools and resources exposed by the MCP server

You have access to a set of tools to read and write VCP values, manage brightness, and refresh the monitor list. Tools include reading a VCP code, writing a VCP value, fetching brightness, and forcing a re-scan of available monitors and codes.

Security considerations

Protect the API endpoint with a strong API key and use MQTT credentials if you enable MQTT. When using remote access, ensure the IP addresses and keys are restricted to trusted devices to prevent unauthorized control of your monitors.

Troubleshooting

If you encounter issues, verify that DDC/CI is enabled in your monitor OSD, confirm the server has access to the monitors, and check that the API key is correct. For MQTT problems, ensure the broker is reachable and credentials match. If commands appear not to work, inspect logs and confirm the monitor supports the requested VCP codes.

Available tools

get_vcp_code

Read a specific VCP code value from a monitor.

set_vcp_code

Write a value to a VCP code on a monitor.

get_brightness

Get the current brightness of the monitor (0-100).

set_brightness

Set the monitor brightness (0-100).

refresh_monitors

Re-scan monitors and their VCP capabilities to update the list.