DDC/CI Control Bridge

Name: DDC/CI Control Bridge
Author: Defozo

Defozo/ddc-ci-control-bridge

5 repo stars
Updated February 2, 2026
Defozo/ddc-ci-control-bridge

DDC/CI Control Bridge is a MCP server that controls monitor brightness, contrast, power, and input via DDC/CI with MCP and MQTT.

About

DDC/CI Control Bridge is an MCP server that exposes display hardware controls over the DDC/CI protocol so agents and scripts can change brightness, contrast, power state, and input selection programmatically. developers who live in AI-assisted IDEs often juggle focus modes, late-night coding, and screen sharing; manually tuning three monitors breaks flow. This bridge (npm identifier ddc-ci-control-bridge, version 1.0.5, stdio transport) gives Claude Code, Cursor, or other MCP hosts a structured tool surface instead of ad-hoc OSD clicks. MQTT support means you can wire the same controls into home-lab or desk automations without building a custom driver stack. Placement in Operate reflects that it maintains your daily workstation—not your SaaS SKU. Requirements are inherently hardware-bound: monitors must speak DDC/CI, OS permissions must allow low-level access, and you should test on one display before automating power toggles on a primary work screen. Treat it as a productivity infra MCP, not a cloud deployment tool.

npm package ddc-ci-control-bridge v1.0.5 with stdio MCP transport
DDC/CI control for brightness, contrast, power, and input switching
Dual exposure: MCP tools for agents plus MQTT support for automation stacks
Useful for multi-monitor indie setups without reaching for vendor-specific GUIs
Open-source bridge on GitHub Defozo/ddc-ci-control-bridge

DDC/CI Control Bridge by the numbers

Data as of Jul 7, 2026 (Skillselion catalog sync)

terminal

claude mcp add ddc-ci-control-bridge -- npx -y ddc-ci-control-bridge

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/mcp/tool/io.github.Defozo/ddc-ci-control-bridge.svg)](https://skillselion.com/mcp/tool/io.github.Defozo/ddc-ci-control-bridge)

repo stars	★ 5
Package	ddc-ci-control-bridge
Transport	STDIO
Auth	None
Last updated	February 2, 2026
Repository	Defozo/ddc-ci-control-bridge ↗

What it does

Let your coding agent adjust monitor brightness, contrast, power, and input over DDC/CI through MCP (and MQTT) from one bridge.

Who is it for?

Best when you have DDC/CI-capable monitors and want agent-driven desk ergonomics and automation hooks.

Skip if: Skip if you're without compatible displays, cloud-only workflows, or teams that forbid local hardware control from agents.

What you get

After install, your agent can call MCP tools (and you can publish MQTT events) to manage display settings from scripts instead of manual OSD menus.

Running stdio MCP server ddc-ci-control-bridge v1.0.5
Agent-callable tools for brightness, contrast, power, and input
Optional MQTT-integrated display control flows

By the numbers

Server version 1.0.5 on npm identifier ddc-ci-control-bridge
Transport type stdio
Controls brightness, contrast, power, and input via DDC/CI

README.md

DDC/CI Control Bridge

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)

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

Option 2: NPX (No Install)

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:

# Set API key (required)
set DDC_API_KEY=your-secret-key

# Run the executable
ddc-ci-bridge-win.exe

# Or set multiple environment variables
set DDC_API_KEY=your-secret-key
set MQTT_ENABLED=true
set MQTT_HOST=192.168.1.100
ddc-ci-bridge-win.exe

Linux/macOS:

# 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 variables
DDC_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:

{
  "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

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

{
  "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)

Add this to your VS Code MCP config file:

"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:

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

Install in Claude Code (Local)

Run this command:

claude mcp add ddc-ci-bridge -- npx -y ddc-ci-control-bridge

Install in Windsurf (Local)

Add this to your Windsurf MCP config file:

{
  "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:

{
  "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:

{
  "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:

{
  "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

Click the hamburger menu
Select Settings
Navigate to Tools section
Click + Add MCP button
Enter command: npx -y ddc-ci-control-bridge
Name: DDC/CI Bridge
Click Add

Option B: Manual Configuration

Add to settings.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)

Go to Settings → Tools → AI Assistant → Model Context Protocol (MCP)
Click + Add
Select As JSON from the dropdown
Add this configuration:

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

Click Apply to save changes

Install in Warp (Local)

Navigate Settings → AI → Manage MCP servers
Click + Add button
Paste this configuration:

{
  "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
  }
}

Click Save

Install in OpenAI Codex (Local)

Add to your Codex MCP configuration:

[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:

[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)

Navigate to Program (right side) → Install → Edit mcp.json
Add this configuration:

{
  "mcpServers": {
    "DDC/CI Bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      }
    }
  }
}

Click Save
Toggle the MCP server on/off from the right side panel

Install in Qodo Gen (Local)

Open Qodo Gen chat panel in VSCode or IntelliJ
Click Connect more tools
Click + Add new MCP
Add this configuration:

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

Install in Perplexity Desktop (Local)

Navigate Perplexity → Settings
Select Connectors
Click Add Connector
Select Advanced
Enter Server Name: DDC/CI Bridge
Paste this JSON:

{
  "command": "npx",
  "args": ["-y", "ddc-ci-control-bridge"],
  "env": {
    "FASTMCP_API_KEY": "your-api-key-here",
    "MQTT_ENABLED": "false"
  }
}

Click Save

Install in Kiro (Local)

Navigate Kiro → MCP Servers
Click + Add button
Paste this configuration:

{
  "mcpServers": {
    "DDC/CI Bridge": {
      "command": "npx",
      "args": ["-y", "ddc-ci-control-bridge"],
      "env": {
        "MQTT_ENABLED": "false"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Click Save

Install in BoltAI (Local)

Open Settings → Plugins
Enter this JSON:

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

Save and restart if needed

Install in Zencoder (Local)

Go to Zencoder menu (...)
Select Agent tools
Click Add custom MCP
Add name and server configuration:

{
  "command": "npx",
  "args": ["-y", "ddc-ci-control-bridge"],
  "env": {
    "FASTMCP_API_KEY": "your-api-key-here",
    "MQTT_ENABLED": "false"
  }
}

Click Install

Install in Amazon Q Developer CLI (Local)

Add to your Amazon Q configuration:

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

Using Bun or Deno

Bun:

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

Deno:

{
  "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):

{
  "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

On the machine with monitors, create a .env file:

DDC_API_KEY=your-secure-random-api-key-here
MCP_TRANSPORT=sse
MCP_PORT=8000

# Optional: Enable MQTT for automation platforms
MQTT_ENABLED=false
MQTT_HOST=localhost
MQTT_PORT=1883

Start the server:

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

Or using npx:

npx ddc-ci-control-bridge

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:

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

VS Code:

"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:

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

Windsurf:

{
  "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

Create a .env file:

cp .env.example .env

Edit .env and configure:

DDC_API_KEY=your-secret-api-key-here

# Enable MQTT for automation platforms (optional)
MQTT_ENABLED=false
MQTT_HOST=localhost
MQTT_PORT=1883

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

Start the server:

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|get
ddc-monitor/{index}/contrast/set|get
ddc-monitor/{index}/vcp/{code}/set|get
ddc-monitor/{index}/power/set
ddc-monitor/{index}/state
ddc-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

npm run build

Build Executables

npm run build:executables

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

Run in Development

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

sudo usermod -a -G i2c $USER
sudo 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

Home Assistant Integration Guide - Complete HA setup
Development Guide - Technical architecture and development details

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

Recommended MCP Servers

0piFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.

100Hires AI ATS & Recruitment SoftwareOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.

123elec McpInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.

1stayHotel booking MCP server.2

2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.4

3D MeshWeaverMesh spatial optimizer reducing geometric overhead in 3D assets.

How it compares

Local hardware bridge MCP server, not a web automation or cloud monitoring integration.

FAQ

Who is DDC/CI Control Bridge for?

It is for developers who want MCP- and MQTT-driven control of monitor brightness, contrast, power, and inputs on DDC/CI-compatible hardware.

When should I use DDC/CI Control Bridge?

Use it in Operate when you are standardizing a multi-monitor desk setup and want agents or automations to adjust displays without manual OSD steps.

How do I add DDC/CI Control Bridge to my agent?

Install npm package ddc-ci-control-bridge, add the stdio MCP server block (v1.0.5) to your client config, restart, and confirm DDC/CI works on your monitors locally first.

Developer Toolsinfra

About

DDC/CI Control Bridge by the numbers

Add your badge

What it does

Who is it for?

What you get

By the numbers

DDC/CI Control Bridge

Features

Quick Start

Installation

MCP Client Setup

🖥️ Local Setup (stdio - Same Machine)

🌐 Remote Setup (HTTP - Different Machines)

Configuration

MQTT Integration

Supported Platforms

MQTT Topics

MCP Resources

MCP Tools

Development

Build

Build Executables

Run in Development

Requirements

Linux Setup

Environment Variables

Architecture

License

Documentation

Contributing

Troubleshooting

No monitors found

MQTT connection failed

Commands not working

Recommended MCP Servers

How it compares

FAQ

Who is DDC/CI Control Bridge for?

When should I use DDC/CI Control Bridge?

How do I add DDC/CI Control Bridge to my agent?

This week in AI coding