DDC/CI Control Bridge
Let your coding agent adjust monitor brightness, contrast, power, and input over DDC/CI through MCP (and MQTT) from one bridge.
Overview
DDC/CI Control Bridge is a MCP server for the Operate phase that controls monitor brightness, contrast, power, and input via DDC/CI with MCP and MQTT.
What is this MCP server?
- 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
- Server version 1.0.5 on npm identifier ddc-ci-control-bridge
- Transport type stdio
- Controls brightness, contrast, power, and input via DDC/CI
Community signal: 5 GitHub stars.
What problem does it solve?
Tweaking multi-monitor brightness and inputs breaks focus when your agent cannot reach standard DDC/CI controls.
Who is it for?
Solo developers with DDC/CI-capable monitors who want agent-driven desk ergonomics and automation hooks.
Skip if: Builders without compatible displays, cloud-only workflows, or teams that forbid local hardware control from agents.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Local hardware control and desk automation sits in Operate when you tune the environment you ship and support from every day. Infra subphase covers machine-adjacent tooling—displays, peripherals, and bridges—not product feature code.
How it compares
Local hardware bridge MCP server, not a web automation or cloud monitoring integration.
Common Questions / 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.