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.
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 serveri2c groupget_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 capabilitiesCompare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| 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 |
{
"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 |
Enables natural language interaction with Home Assistant entities using the Model Context Protocol.
Integrates with Home Assistant to provide smart home control capabilities via Model Context Protocol (MCP).
A Model Context Protocol (MCP) server that enables AI agents to interact with the 1NCE IoT connectivity management platform through natural language.
Check AI crawler robots.txt policy and monitor public-site policy, sitemap, and llms.txt changes.
FX and metals market data: plans, 51 symbols, price quotes, and candles with an API key.
Bounded crawl-readiness check for agent access: robots.txt, sitemap.xml, llms.txt, homepage.