Debmatic MCP Server

MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API

Local serverstdio

What is the Debmatic MCP server?

MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API. Exposed over MCP by the debmatic mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Talk to your HomeMatic smart home from Claude, Cursor, or any MCP client.

Configuration

You will need 7 environment variables: CCU_HOST, CCU_PASSWORD, MCP_AUTH_TOKEN, MCP_TLS_KEY, CCU_PROD_HOST, CCU_DEV_HOST, CCU__HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • A running HomeMatic CCU (debmatic, CCU3, or OpenCCU — formerly RaspberryMatic) reachable on your network - The CCU's admin username and password (the same credentials you use to log into the WebUI) - Node.js 24+ (for running from source or stdio mode) or Docker

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at ccu-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by claymore666; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Debmatic's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the debmatic mcp server does with a few real requests.

How to install the Debmatic MCP server

{
  "mcpServers": {
    "debmatic": {
      "command": "npx",
      "args": ["-y", "ccu-mcp"],
      "env": {
        "CCU_HOST": "your-value",
        "CCU_PASSWORD": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "MCP_TLS_KEY": "your-value",
        "CCU_PROD_HOST": "your-value",
        "CCU_DEV_HOST": "your-value",
        "CCU__HOST": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • A running HomeMatic CCU (debmatic, CCU3, or OpenCCU — formerly RaspberryMatic) reachable on your network - The CCU's admin username and password (the same credentials you use to log into the WebUI) - Node.js 24+ (for running from source or stdio mode) or Docker
VariableDescriptionRequired
CCU_HOSTEndpoint or connection string the server talks to.Optional
CCU_PASSWORDConfiguration value read at startup.Optional
MCP_AUTH_TOKENCredential the server authenticates with.Yes
MCP_TLS_KEYCredential the server authenticates with.Yes
CCU_PROD_HOSTEndpoint or connection string the server talks to.Optional
CCU_DEV_HOSTEndpoint or connection string the server talks to.Optional
CCU__HOSTEndpoint or connection string the server talks to.Optional

Frequently asked questions

It connects Debmatic to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Debmatic directly.