Debmatic MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 70 installs a week from npm. Last commit 3 Nov 2026.
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
What the code does
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет debmatic-mcp ссылается на claymore666/debmatic-mcp
for (const key of Object.keys(process.env)) {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add debmatic-mcp -e 'CCU_HOST=<CCU_HOST>' -e 'CCU_PASSWORD=<CCU_PASSWORD>' -- npx -y debmatic-mcp{
"mcpServers": {
"debmatic-mcp": {
"command": "npx",
"args": [
"-y",
"debmatic-mcp"
],
"env": {
"CCU_HOST": "<CCU_HOST>",
"CCU_PASSWORD": "<CCU_PASSWORD>"
}
}
}
}[mcp_servers.debmatic-mcp]
command = "npx"
args = ["-y", "debmatic-mcp"]
env = { CCU_HOST = "<CCU_HOST>", CCU_PASSWORD = "<CCU_PASSWORD>" }{
"mcpServers": {
"debmatic-mcp": {
"command": "npx",
"args": [
"-y",
"debmatic-mcp"
],
"env": {
"CCU_HOST": "<CCU_HOST>",
"CCU_PASSWORD": "<CCU_PASSWORD>"
}
}
}
}{
"servers": {
"debmatic-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"debmatic-mcp"
],
"env": {
"CCU_HOST": "<CCU_HOST>",
"CCU_PASSWORD": "<CCU_PASSWORD>"
}
}
}
}Put your own values in place of
<CCU_HOST> (Hostname or IP of your HomeMatic CCU (debmatic, CCU3, or RaspberryMatic)), <CCU_PASSWORD> (CCU admin password (same as the WebUI login)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CCU_USER (CCU username), CCU_HTTPS (Connect to the CCU via HTTPS (self-signed certificates supported)), CCU_PORT (CCU API port (80 for HTTP, 443 for HTTPS)), CACHE_DIR (Directory for the device type cache and session persistence), MCP_ALLOWED_ORIGINS (Comma-separated allowlist of browser origins. Unset = no cross-origin browser access (default-deny). An allowlisted origin is reflected exactly in Access-Control-Allow-Origin (never '*'); the list also drives DNS-rebinding origin checks), MCP_ALLOWED_HOSTS (Extra Host header values accepted by DNS-rebinding protection (comma-separated host:port); add your hostname when behind a proxy or container DNS name).
Alternatives to Debmatic MCP
same job, measured the same wayMCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents
MCP server for Hubitat: devices, status, commands via Maker API. Local-first smart home.
MCP server for Tasmota devices: status, power control. Local-first smart home.
Local-first MCP server for Shelly smart-home devices (Gen1-Gen4): control, energy, automation.
MCP server for controlling Discord servers via bot token
MCP server for Android device control via ADB and scrcpy
MCP server for controlling the Xojo IDE on macOS
Debmatic MCP — questions
Answers built from our own checks of this server.