ddc-ci-control-bridge

The DDC/CI Control Bridge is a multi-protocol MCP server that enables both local DDC/CI monitor control and MQTT-based automation. It exposes tools to read and write VCP codes for monitor brightness, contrast, input source, and other display parameters, and it integrates with the MCP framework so AI agents and automation systems can discover and interact with it using standard MCP resources and MQTT pub/sub. With the included MQTT support you can enable Home Assistant auto-discovery and publish/subscribe to topics for monitor control, status, and telemetry. You can run the server via NPX or install it globally, then connect using an MCP client to see a list of available resources, commands, and any provided endpoints for DDC/CI actions, model context resources, and MQTT messaging. The server is designed to be cross-platform and can operate either as a local stdio-based MCP server or via an HTTP/remote MCP setup depending on your integration needs.

Prerequisites:

• Node.js and npm installed on your system (for npm/NPX usage).
• Access to a monitor that supports DDC/CI if you plan to test brightness/contrast controls locally.

Installation options:

Option 1: Install globally (via npm) and run

npm install -g ddc-ci-control-bridge
ddc-ci-bridge

Option 2: Run with NPX (no install)

npx ddc-ci-control-bridge

Option 3: Download standalone executable (prebuilt binaries) from GitHub Releases and run

• Windows: ddc-ci-bridge-win.exe
• Linux: ddc-ci-bridge-linux
• macOS: ddc-ci-bridge-macos

Notes:

• The standalone executable requires DDC_API_KEY to be set in the environment. Without it, the binary will exit.
• If you’re using MCP, you can configure the server entry via npx as shown in the MCP config example below.

Example MCP client configuration (local stdio setup):

{
  "mcpServers": {
    "ddc-ci-bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false",
        "MQTT_HOST": "localhost",
        "MQTT_PORT": "1883"
      }
    }
  }
}

Tips and common considerations:

• If using the standalone binary, remember to set DDC_API_KEY if required by your build, or the binary will refuse to start.
• For MCP integrations, MQTT can be toggled via MQTT_ENABLED and configured with MQTT_HOST/PORT as needed. If you’re not using MQTT, you can disable it to reduce overhead.
• The MCP configuration shown uses the command path npx -y ddc-ci-control-bridge; you can adjust the command/args if you prefer a local install or a different MCP client setup.
• Ensure your environment has access to the display/monitor you intend to control; DDC/CI requires proper hardware support and permissions on some platforms.
• When testing VCP read/write operations, start with non-destructive values to avoid unintended display changes.