Debmatic MCP vs Shelly Smart Home
A side-by-side look at the Debmatic MCP and Shelly Smart Home MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Debmatic MCP for home automation work as a local process; choose Shelly Smart Home 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 Debmatic MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
CCU_HOST, CCU_PASSWORD.
Choose Shelly Smart Home when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 59/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | CCU_HOSTCCU_PASSWORD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Debmatic MCP | View Shelly Smart Home |
Tools & capabilities
Debmatic MCP tools
No tool names declared yet. Check the project README from the listing page.
Shelly Smart Home 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.
Debmatic MCP
{
"mcpServers": {
"claymore666-debmatic-mcp": {
"command": "npx",
"args": [
"-y",
"ccu-mcp"
],
"env": {
"CCU_HOST": "YOUR_CCU_HOST_HERE",
"CCU_PASSWORD": "YOUR_CCU_PASSWORD_HERE"
}
}
}
}
Shelly Smart Home
{
"mcpServers": {
"shelly-smart-home": {
"command": "uvx",
"args": [
"shelly-mcp"
]
}
}
}
Frequently asked questions
Debmatic MCP is categorized under Home Automation and uses a local stdio subprocess. Shelly Smart Home belongs to Home Automation and uses a local stdio subprocess. Pick Debmatic MCP for home automation work and Shelly Smart Home 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.
Debmatic MCP is listed as free. Auth: other. Shelly Smart Home 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 claymore666-debmatic-mcp and shelly-smart-home as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Debmatic MCP has a quality signal of 59/100 (Good) with 1 views, 0 installs and 9 GitHub stars. Shelly Smart Home has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.