# DDC/CI Control Bridge [Health: Active] **Category:** 🏠 Home Automation **Repository:** https://github.com/Defozo/ddc-ci-control-bridge **GitHub Stars:** 5 **Views:** 2 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/ddc-ci-control-bridge ## Description Control monitor brightness, contrast, power and input via DDC/CI with MCP and MQTT support. ## Tools Capabilities this server exposes over MCP: - **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 ## Claude Desktop Quick Installation Install path detected from listing signals. Uses `npx` (confidence: high): ```json "mcpServers": { "ci-control-bridge": { "command": "npx", "args": ["-y","ddc-ci-control-bridge"] } } ``` ## Documentation & README # DDC/CI Control Bridge ![DDC/CI Control Bridge](docs/banner.png) [![NPM Version](https://img.shields.io/npm/v/ddc-ci-control-bridge?color=red)](https://www.npmjs.com/package/ddc-ci-control-bridge) [![MIT licensed](https://img.shields.io/github/license/Defozo/ddc-ci-control-bridge)](./LICENSE) [![GitHub Release](https://img.shields.io/github/v/release/Defozo/ddc-ci-control-bridge)](https://github.com/Defozo/ddc-ci-control-bridge/releases) [![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=ddc-ci-bridge&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRkYy1jaS1jb250cm9sLWJyaWRnZSJdfQ%3D%3D) [Install in VS Code](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%7B%22name%22%3A%22ddc-ci-bridge%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22ddc-ci-control-bridge%22%5D%7D) 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-bridge ddc-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](https://github.com/Defozo/ddc-ci-control-bridge/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 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:** ```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 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: ```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](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=ddc-ci-bridge&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRkYy1jaS1jb250cm9sLWJyaWRnZSJdfQ%3D%3D) 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](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%7B%22name%22%3A%22ddc-ci-bridge%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22ddc-ci-control-bridge%22%5D%7D) 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" } } } } ``` 5. 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 } } ``` 4. 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" } } } } ``` 3. Click `Save` 4. 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" } } ``` 7. 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": [] } } } ``` 4. 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" } } } } ``` 3. 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" } } ``` 5. 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-here MCP_TRANSPORT=sse MCP_PORT=8000 # Optional: Enable MQTT for automation platforms MQTT_ENABLED=false MQTT_HOST=localhost MQTT_PORT=1883 ``` 2. Start the server: ```bash npm install -g ddc-ci-control-bridge ddc-ci-bridge ``` Or using npx: ```bash npx ddc-ci-control-bridge ``` 3. 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 ``` 2. Edit `.env` and configure: ```bash 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). 3. 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](./docs/README-HOMEASSISTANT.md) - **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 ```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 $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](./docs/README-HOMEASSISTANT.md) - Complete HA setup - [Development Guide](./docs/DEVELOPMENT.md) - 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