CI Control Bridge vs Ha MCP
A side-by-side look at the CI Control Bridge and Ha MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CI Control Bridge for home automation work as a local process; choose Ha MCP for home automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CI Control Bridge when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DDC_API_KEY, MQTT_ENABLED, MQTT_HOST. - You want tools like
get_vcp_code, set_vcp_code, get_brightness.
Choose Ha MCP when
- You need dedicated capabilities in the Home Automation domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
HOMEASSISTANT_URL, HOMEASSISTANT_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 55/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | DDC_API_KEYMQTT_ENABLEDMQTT_HOST | HOMEASSISTANT_URLHOMEASSISTANT_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 5,186 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View CI Control Bridge | View Ha MCP |
Tools & capabilities
CI Control Bridge tools 5
get_vcp_codeRead a specific VCP code valueset_vcp_codeWrite a value to a VCP codeget_brightnessGet monitor brightness (0-100)set_brightnessSet monitor brightness (0-100)refresh_monitorsRe-scan monitors and VCP capabilities
Ha MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
CI Control Bridge
{
"mcpServers": {
"ddc-ci-control-bridge": {
"command": "npx",
"args": [
"-y",
"ddc-ci-control-bridge"
],
"env": {
"DDC_API_KEY": "YOUR_DDC_API_KEY_HERE",
"MQTT_ENABLED": "YOUR_MQTT_ENABLED_HERE",
"MQTT_HOST": "YOUR_MQTT_HOST_HERE"
}
}
}
}
Ha MCP
No confirmed install command for Ha MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
CI Control Bridge is categorized under Home Automation and uses a local stdio subprocess. Ha MCP belongs to Home Automation and uses an install path we have not confirmed yet. Pick CI Control Bridge for home automation work and Ha MCP for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Ha MCP has no confirmed install command yet — follow its own setup instructions.
CI Control Bridge is listed as free. Auth: api key required. Ha MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ddc-ci-control-bridge and ha-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CI Control Bridge has a quality signal of 55/100 (Good) with 4 views, 0 installs and 5 GitHub stars. Ha MCP has 44/100 (Fair) with 0 views, 0 installs and 5,186 GitHub stars.