DDC/CI Control Bridge

io.github.DefozoPublished by GitHub account Defozov1.0.5Updated Oct 24, 2026

Control monitor brightness, contrast, power and input via DDC/CI with MCP and MQTT support.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant read and change physical monitor settings over DDC/CI, such as brightness, contrast, input source and power.

What you can do
Read and write monitor VCP codes, including brightness and contrast values and other supported codes, and set the input source or power state where the monitor allows it. List connected monitors and re-scan them together with their supported VCP capabilities. Read monitor metadata and current values for all supported codes as MCP resources. Optionally publish and subscribe over MQTT, with Home Assistant auto-discovery, so the same controls can be driven from automation platforms.
When to use it
Use it when you want an assistant to adjust or inspect the physical display attached to the machine, for example dimming a monitor, switching inputs, or checking which VCP codes a display supports. It is also useful if you want monitor controls exposed to Home Assistant or another MQTT automation platform.
Requirements
Runs as a local process on the machine connected to the monitors, via npm, npx or a standalone executable; Node.js is needed for the npm route. Monitors must support DDC/CI and have it enabled in their on-screen settings. On Linux, the user may need to be in the i2c group and the i2c-dev module loaded. The standalone executable requires the DDC_API_KEY environment variable. Optional MQTT settings include MQTT_ENABLED, MQTT_HOST and MQTT_PORT.
Before you install
The server changes real hardware state: setting VCP codes, brightness, input source or power affects the physical display and can blank or switch off a screen. The standalone executable exits unless DDC_API_KEY is set, and the README also shows an API key in client configurations; treat it as a secret. Enabling MQTT connects to a broker and publishes monitor state and control topics, so point it only at a broker you trust. The README suggests elevated permissions as a troubleshooting step, which

Installation

In SourceWeft

  1. Open DDC/CI Control Bridge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

DDC/CI Control Bridge

[DDC/CI Control Bridge]

[NPM Version] [MIT licensed] [GitHub Release]

[Install MCP Server] [Install in VS Code]

Multi-protocol server for DDC/CI monitor control with MCP and MQTT support.

Features

  • DDC/CI Monitor Control: Read and write VCP codes to control monitor brightness, contrast, input source, and more
  • Model Context Protocol (MCP): Server with resources and tools for AI/agent integration
  • MQTT Client: Connect to any MQTT broker for IoT/automation platforms
    • Home Assistant auto-discovery support
    • Generic MQTT pub/sub for custom integrations
  • Cross-Platform: Works on Windows, Linux, and macOS
  • Dual Distribution: Available as standalone executable or npm package

Quick Start

Installation

Option 1: NPM Package (Global)

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

Option 2: NPX (No Install)

bash
npx ddc-ci-control-bridge

Option 3: Standalone Executable

Download the binary for your platform from GitHub Releases:

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

⚠️ Note: The executable requires DDC_API_KEY environment variable to be set, or it will exit immediately.

Windows:

cmd
# Set API key (required)set DDC_API_KEY=your-secret-key
# Run the executableddc-ci-bridge-win.exe
# Or set multiple environment variablesset DDC_API_KEY=your-secret-keyset MQTT_ENABLED=trueset MQTT_HOST=192.168.1.100ddc-ci-bridge-win.exe

Linux/macOS:

bash
# Make executable (first time only)chmod +x ddc-ci-bridge-linux  # or ddc-ci-bridge-macos
# Run with API key (required)DDC_API_KEY=your-secret-key ./ddc-ci-bridge-linux
# Or with multiple environment variablesDDC_API_KEY=your-secret-key MQTT_ENABLED=true MQTT_HOST=192.168.1.100 ./ddc-ci-bridge-linux

Using with MCP Clients:

Configure your MCP client to use the executable path:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "C:\\path\\to\\ddc-ci-bridge-win.exe",      "args": [],      "env": {        "MQTT_ENABLED": "false"      }    }  }}

MCP Client Setup

Choose between Local (stdio) or Remote (HTTP) setup depending on your needs:

  • Local Setup: Run MCP server on the same machine as your monitors (recommended for most users)
  • Remote Setup: Run MCP server on a monitor-connected machine, access from other devices
🖥️ Local Setup (stdio - Same Machine)

Use this if your MCP client is on the same machine as your monitors.

Install in Cursor (Local)

Go to: Settings → Cursor Settings → MCP → Add new global MCP server

[Install MCP Server]

Or paste the following configuration into your ~/.cursor/mcp.json file:

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

Optional MQTT: Set MQTT_ENABLED=true and configure MQTT_HOST to your MQTT broker IP for automation platform integration.

Install in VS Code (Local)

[Install in VS Code]

Add this to your VS Code MCP config file:

json
"mcp": {  "servers": {    "ddc-ci-bridge": {      "type": "stdio",      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Claude Desktop (Local)

Open Claude Desktop developer settings and edit your claude_desktop_config.json file:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Claude Code (Local)

Run this command:

sh
claude mcp add ddc-ci-bridge -- npx -y ddc-ci-control-bridge
Install in Windsurf (Local)

Add this to your Windsurf MCP config file:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Cline (Local)

Add this to your Cline MCP configuration:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Zed (Local)

Add this to your Zed settings.json:

json
{  "context_servers": {    "DDC/CI Bridge": {      "source": "custom",      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Roo Code (Local)

Add this to your Roo Code MCP configuration:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Augment Code (Local)

Option A: Using the UI

  1. Click the hamburger menu
  2. Select Settings
  3. Navigate to Tools section
  4. Click + Add MCP button
  5. Enter command: npx -y ddc-ci-control-bridge
  6. Name: DDC/CI Bridge
  7. Click Add

Option B: Manual Configuration

Add to settings.json:

json
"augment.advanced": {  "mcpServers": [    {      "name": "ddc-ci-bridge",      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  ]}
Install in JetBrains AI Assistant (Local)
  1. Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP)
  2. Click + Add
  3. Select As JSON from the dropdown
  4. Add this configuration:
json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
  1. Click Apply to save changes
Install in Warp (Local)
  1. Navigate Settings → AI → Manage MCP servers
  2. Click + Add button
  3. Paste this configuration:
json
{  "DDC/CI Bridge": {    "command": "npx",    "args": ["-y", "ddc-ci-control-bridge"],    "env": {      "FASTMCP_API_KEY": "your-api-key-here",      "MQTT_ENABLED": "false"    },    "working_directory": null,    "start_on_launch": true  }}
  1. Click Save
Install in OpenAI Codex (Local)

Add to your Codex MCP configuration:

toml
[mcp_servers.ddc-ci-bridge]command = "npx"args = ["-y", "ddc-ci-control-bridge"]
[mcp_servers.ddc-ci-bridge.env]MQTT_ENABLED = "false"

Windows Users: Use full paths if you encounter timeout errors:

toml
[mcp_servers.ddc-ci-bridge]command = "cmd"args = ["/c", "npx", "-y", "ddc-ci-control-bridge"]startup_timeout_ms = 20_000
[mcp_servers.ddc-ci-bridge.env]SystemRoot = "C:\\Windows"FASTMCP_API_KEY = "your-api-key-here"MQTT_ENABLED = "false"
Install in LM Studio (Local)
  1. Navigate to Program (right side) → Install → Edit mcp.json
  2. Add this configuration:
json
{  "mcpServers": {    "DDC/CI Bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
  1. Click Save
  2. Toggle the MCP server on/off from the right side panel
Install in Qodo Gen (Local)
  1. Open Qodo Gen chat panel in VSCode or IntelliJ
  2. Click Connect more tools
  3. Click + Add new MCP
  4. Add this configuration:
json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Install in Perplexity Desktop (Local)
  1. Navigate Perplexity → Settings
  2. Select Connectors
  3. Click Add Connector
  4. Select Advanced
  5. Enter Server Name: DDC/CI Bridge
  6. Paste this JSON:
json
{  "command": "npx",  "args": ["-y", "ddc-ci-control-bridge"],  "env": {    "FASTMCP_API_KEY": "your-api-key-here",    "MQTT_ENABLED": "false"  }}
  1. Click Save
Install in Kiro (Local)
  1. Navigate Kiro → MCP Servers
  2. Click + Add button
  3. Paste this configuration:
json
{  "mcpServers": {    "DDC/CI Bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      },      "disabled": false,      "autoApprove": []    }  }}
  1. Click Save
Install in BoltAI (Local)
  1. Open Settings → Plugins
  2. Enter this JSON:
json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
  1. Save and restart if needed
Install in Zencoder (Local)
  1. Go to Zencoder menu (...)
  2. Select Agent tools
  3. Click Add custom MCP
  4. Add name and server configuration:
json
{  "command": "npx",  "args": ["-y", "ddc-ci-control-bridge"],  "env": {    "FASTMCP_API_KEY": "your-api-key-here",    "MQTT_ENABLED": "false"  }}
  1. Click Install
Install in Amazon Q Developer CLI (Local)

Add to your Amazon Q configuration:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "npx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Using Bun or Deno

Bun:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "bunx",      "args": ["-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      }    }  }}

Deno:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "deno",      "args": [        "run",        "--allow-env",        "--allow-net",        "npm:ddc-ci-control-bridge"      ],      "env": {        "MQTT_ENABLED": "false"      }    }  }}
Windows-Specific Configuration

On Windows, use this format (example with Cline):

json
{  "mcpServers": {    "ddc-ci-bridge": {      "command": "cmd",      "args": ["/c", "npx", "-y", "ddc-ci-control-bridge"],      "env": {        "MQTT_ENABLED": "false"      },      "disabled": false,      "autoApprove": []    }  }}
🌐 Remote Setup (HTTP - Different Machines)

Use this if you want to access monitor controls from a different machine on your network.

Step 1: Set up the MCP Server on Monitor-Connected Machine
  1. On the machine with monitors, create a .env file:
bash
DDC_API_KEY=your-secure-random-api-key-hereMCP_TRANSPORT=sseMCP_PORT=8000
# Optional: Enable MQTT for automation platformsMQTT_ENABLED=falseMQTT_HOST=localhostMQTT_PORT=1883
  1. Start the server:
bash
npm install -g ddc-ci-control-bridgeddc-ci-bridge

Or using npx:

bash
npx ddc-ci-control-bridge
  1. The server will display:
🔌 MCP Server: http://192.168.1.100:8000   Transport: sse   API Key: your-api...

Note the IP address and port for client configuration.

Step 2: Configure MCP Clients (Remote Connection)

Cursor:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "url": "http://192.168.1.100:8000",      "headers": {        "Authorization": "Bearer your-secure-random-api-key-here"      }    }  }}

VS Code:

json
"mcp": {  "servers": {    "ddc-ci-bridge": {      "type": "http",      "url": "http://192.168.1.100:8000",      "headers": {        "Authorization": "Bearer your-secure-random-api-key-here"      }    }  }}

Claude Desktop:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "url": "http://192.168.1.100:8000",      "headers": {        "Authorization": "Bearer your-secure-random-api-key-here"      }    }  }}

Windsurf:

json
{  "mcpServers": {    "ddc-ci-bridge": {      "serverUrl": "http://192.168.1.100:8000",      "headers": {        "Authorization": "Bearer your-secure-random-api-key-here"      }    }  }}

Note: Replace 192.168.1.100 with the actual IP address of your monitor-connected machine, and use the same API key you configured in the server's .env file.

Configuration

  1. Create a .env file:
bash
cp .env.example .env
  1. Edit .env and configure:
bash
DDC_API_KEY=your-secret-api-key-here
# Enable MQTT for automation platforms (optional)MQTT_ENABLED=falseMQTT_HOST=localhostMQTT_PORT=1883

To enable MQTT: Set MQTT_ENABLED=true and change MQTT_HOST to your MQTT broker IP (e.g., Home Assistant IP).

  1. Start the server:
bash
npm run dev

MQTT Integration

This server acts as an MQTT client and can connect to any MQTT broker.

Supported Platforms

  • Home Assistant: Auto-discovery via MQTT Discovery Protocol → See Home Assistant Guide
  • openHAB: MQTT binding with manual thing configuration
  • Node-RED: Subscribe to topics for custom flows
  • Domoticz: MQTT integration
  • Generic MQTT: Any platform that supports MQTT pub/sub

MQTT Topics

ddc-monitor/{index}/brightness/set|getddc-monitor/{index}/contrast/set|getddc-monitor/{index}/vcp/{code}/set|getddc-monitor/{index}/power/setddc-monitor/{index}/stateddc-monitor/bridge/status

MCP Resources

  • monitor://list - List all available monitors
  • monitor://{index}/capabilities - Full VCP code scan results
  • monitor://{index}/current-values - Current values of all supported codes
  • monitor://{index}/info - Monitor metadata

MCP Tools

  • get_vcp_code - Read a specific VCP code value
  • set_vcp_code - Write a value to a VCP code
  • get_brightness - Get monitor brightness (0-100)
  • set_brightness - Set monitor brightness (0-100)
  • refresh_monitors - Re-scan monitors and VCP capabilities

Development

Build

bash
npm run build

Build Executables

bash
npm run build:executables

This creates standalone executables in dist/bin/ for Windows, Linux, and macOS.

Run in Development

bash
npm run dev

Requirements

  • DDC/CI Support: Your monitor must support DDC/CI (most modern monitors do)
  • DDC/CI Enabled: Enable DDC/CI in your monitor's OSD settings
  • Permissions: On Linux, you may need to add your user to the i2c group

Linux Setup

bash
sudo usermod -a -G i2c $USERsudo modprobe i2c-dev

Log out and log back in for group changes to take effect.

Environment Variables

See .env.example for all available configuration options.

Key variables:

  • DDC_API_KEY - API key for server authentication (required)
  • MCP_TRANSPORT - Transport type: sse or stdio (default: sse)
  • MCP_PORT - HTTP port for SSE transport (default: 8000)
  • MQTT_ENABLED - Enable MQTT client (default: false)
  • MQTT_HOST - MQTT broker IP/hostname (default: localhost)
  • MQTT_PORT - MQTT broker port (default: 1883)
  • MQTT_USERNAME - Auto-configured as ddc-mcp
  • MQTT_PASSWORD - Auto-configured from DDC_API_KEY

Architecture

┌─────────────────────────────────────────┐│       DDC/CI Control Bridge             ││                                         ││  ┌─────────────────┐  ┌──────────────┐ ││  │  MCP Server     │  │ MQTT Client  │ ││  │  - Resources    │  │ - Pub/Sub    │ ││  │  - Tools        │  │ - Discovery  │ ││  └────────┬────────┘  └──────┬───────┘ ││           │                  │         ││           └────────┬─────────┘         ││                    │                   ││           ┌────────▼────────┐          ││           │ DDC Controller  │          ││           │ - VCP Scanning  │          ││           │ - Read/Write    │          ││           └────────┬────────┘          │└────────────────────┼───────────────────┘                     │            ┌────────▼────────┐            │ Physical Monitor│            │   (DDC/CI)      │            └─────────────────┘
External Clients:┌──────────────┐  ┌──────────────┐  ┌──────────────┐│ AI Agents    │  │ MQTT Broker  │  │ Automation   ││ (via MCP)    │  │ (any broker) │  │ Platforms    │└──────────────┘  └──────────────┘  └──────────────┘

License

MIT

Documentation

Contributing

Contributions welcome! Please open an issue or PR.

Troubleshooting

No monitors found

  • Ensure DDC/CI is enabled in your monitor's OSD settings
  • On Linux, check if i2c devices are available: ls -l /dev/i2c-*
  • Try running with elevated permissions (not recommended for production)

MQTT connection failed

  • Verify MQTT broker is running
  • Check credentials match the server output
  • Ensure firewall allows MQTT port (1883)

Commands not working

  • Check server logs for errors
  • Verify monitor supports the VCP code
  • Some codes may be read-only
  • Try restarting both server and Home Assistant

Source: README.md at commit 23a3e00

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts