Control monitor brightness, contrast, power and input via DDC/CI with MCP and MQTT support.
Control monitor brightness, contrast, power and input via DDC/CI with MCP and MQTT support. That is what the ddc/ci control bridge mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 8 tools. What each one is for:
get_vcp_code — Read a specific VCP code valueset_vcp_code — Write a value to a VCP codeget_brightness — Get monitor brightness (0-100)set_brightness — Set monitor brightness (0-100)refresh_monitors — Re-scan monitors and VCP capabilitiesInstallation — Download the binary for your platform from GitHub Releases:Configuration — 2. Edit .env and configure: bash DDC_API_KEY=your-secret-api-key-hereBuild — The Build tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at ddc-ci-control-bridge on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: MQTT_ENABLED, MQTT_HOST, MQTT_PORT, FASTMCP_API_KEY, DDC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
i2c groupPlenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. DDC/CI Control Bridge's toolset — get_vcp_code, set_vcp_code, get_brightness and 5 more — is a fair guide to whether it matches your workflow. It is maintained by Defozo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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 |
| Installation | Download the binary for your platform from [GitHub Releases](https://github.com/Defozo/ddc-ci-control-bridge/releases): |
| Configuration | 2. Edit .env and configure: bash DDC_API_KEY=your-secret-api-key-here |
| Build | The Build tool exposed by this server. |
{
"mcpServers": {
"ddc-ci-bridge": {
"command": "C:\\path\\to\\ddc-ci-bridge-win.exe",
"args": [],
"env": {
"MQTT_ENABLED": "false"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
i2c group| Variable | Description | Required |
|---|---|---|
| MQTT_ENABLED | Configuration value read at startup. | Optional |
| MQTT_HOST | Endpoint or connection string the server talks to. | Optional |
| MQTT_PORT | Configuration value read at startup. | Optional |
| FASTMCP_API_KEY | Credential the server authenticates with. | Yes |
| DDC_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.