Ccu MCP vs Homeassistant MCP
A side-by-side look at the Ccu MCP and Homeassistant MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ccu MCP for home automation work as a local process; choose Homeassistant MCP for home automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ccu MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CCU_HOST, CCU_PASSWORD.
Choose Homeassistant 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:
HASS_HOST, HASS_TOKEN, HASS_SOCKET_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 45/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | CCU_HOSTCCU_PASSWORD | HASS_HOSTHASS_TOKENHASS_SOCKET_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 575 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Ccu MCP | View Homeassistant MCP |
Tools & capabilities
Ccu MCP tools
No tool names declared yet. Check the project README from the listing page.
Homeassistant 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.
Ccu MCP
{
"mcpServers": {
"ccu-mcp": {
"command": "npx",
"args": [
"-y",
"ccu-mcp"
],
"env": {
"CCU_HOST": "YOUR_CCU_HOST_HERE",
"CCU_PASSWORD": "YOUR_CCU_PASSWORD_HERE"
}
}
}
}
Homeassistant MCP
No confirmed install command for Homeassistant MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Ccu MCP is categorized under Home Automation and uses a local stdio subprocess. Homeassistant MCP belongs to Home Automation and uses an install path we have not confirmed yet. Pick Ccu MCP for home automation work and Homeassistant 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. Homeassistant MCP has no confirmed install command yet — follow its own setup instructions.
Ccu MCP has no declared pricing — check the project's own site. Homeassistant 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 ccu-mcp and tevonsb-homeassistant-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ccu MCP has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 9 GitHub stars. Homeassistant MCP has 40/100 (Fair) with 4 views, 0 installs and 575 GitHub stars.