CI Control Bridge vs Home Assistant MCP
A side-by-side look at the CI Control Bridge and Home Assistant MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Home Assistant MCPHome Automation · Local subprocess (stdio)Home Assistant and ESPHome for coding agents: states, services, automations, dashboards, flashing.56GoodAuth: not declaredVerdict: choose CI Control Bridge for home automation work as a local process; choose Home Assistant MCP for home automation as a local process. 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.
HChoose Home Assistant MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ha_get_config, ha_list_entities, ha_get_state.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Home Assistant MCP | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 53/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | DDC_API_KEYMQTT_ENABLEDMQTT_HOST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 80 |
| Full listing | View CI Control Bridge | View Home Assistant 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
Home Assistant MCP tools 80
ha_get_configCore config: version, location, time zone, loaded components.ha_list_entitiesList entities (filter by domain, free-text search, area).ha_get_stateFull state + attributes for one or more entities.ha_get_historyHistorical state changes over a time window. Given only a start time, it runs up to now (Home Assistant alone stops 24 hours after the start); `ha_get_logbook` does the same.ha_list_servicesAvailable services (and their fields for a given domain).ha_list_areasAreas (rooms/zones).ha_list_devicesDevice registry (filter by area / search).ha_get_entity_registryRegistry metadata: platform, area, device, disabled/hidden.ha_render_templateRender a Jinja2 template against live state.ha_list_helpersList stored helpers (input_boolean, input_number, counter, timer, …).ha_list_automationsAutomations with entity_id, unique id, state, last-triggered.ha_get_automationFull automation config (triggers/conditions/actions).- +68 more on 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"
}
}
}
}
Home Assistant MCP
{
"mcpServers": {
"home-assistant-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vortitron/home-assistant-mcp"
]
}
}
}
Frequently asked questions
CI Control Bridge is categorized under Home Automation and uses a local stdio subprocess. Home Assistant MCP belongs to Home Automation and uses a local stdio subprocess. Pick CI Control Bridge for home automation work and Home Assistant 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.
CI Control Bridge is listed as free. Auth: api key required. Home Assistant MCP has no declared pricing — check the project's own site. 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 home-assistant-mcp-2 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 53/100 (Good) with 3 views, 0 installs and 5 GitHub stars. Home Assistant MCP has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.