ccu-mcp
io.github.claymore666/ccu-mcp
About ccu-mcp
ccu-mcp is an MCP server published by the GitHub account claymore666. MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
It runs on your own machine: your AI client starts it from the npm package ccu-mcp at version 1.11.7.
It asks for one secret: CCU_PASSWORD. Give it a key with the least access that still works.
It also needs CCU_HOST set before it starts.
Version 1.11.7 was published on 25 October 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
CCU_HOST | Yes | No | Hostname or IP of your HomeMatic CCU (debmatic, CCU3, or OpenCCU/RaspberryMatic) |
CCU_PASSWORD | Yes | Yes | CCU admin password (same as the WebUI login). Must be set; the value may be empty for a CCU with no password |
CCU_USER | No | No | CCU username |
CCU_HTTPS | No | No | Connect to the CCU via HTTPS (self-signed certificates supported) |
CCU_PORT | No | No | CCU API port (80 for HTTP, 443 for HTTPS) |
CACHE_DIR | No | No | Directory for the device type cache and session persistence |
MCP_ALLOWED_ORIGINS | No | No | 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 | No | No | Extra Host header values accepted by DNS-rebinding protection (comma-separated host:port); add your hostname when behind a proxy or container DNS name |
CCU_PROFILES | No | No | Comma-separated names of multiple CCU targets (e.g. 'prod,dev'). Each profile takes the flat CCU_* settings prefixed CCU_<NAME>_ (CCU_PROD_HOST, ...), plus policy flags CCU_<NAME>_PROTECTED (writes need confirm:true) and CCU_<NAME>_READONLY. Unset = single default profile from the flat CCU_* vars |
CCU_DEFAULT_PROFILE | No | No | Which profile from CCU_PROFILES is active at startup (default: the first listed) |
CCU_TLS_VERIFY | No | No | Verify the CCU's TLS certificate against the system trust store. Only meaningful with CCU_HTTPS=true. Default false, because a CCU ships a self-signed certificate — prefer CCU_TLS_FINGERPRINT or CCU_CA_CERT to verify one of those |
CCU_TLS_FINGERPRINT | No | No | Pin the CCU's self-signed leaf certificate by its SHA-256 fingerprint (hex, colons optional). The strongest option for an appliance: the connection is rejected unless the presented certificate matches. Takes precedence over CCU_CA_CERT |
CCU_CA_CERT | No | No | Path to a PEM file holding the CCU's CA or self-signed certificate. The connection is then validated against it with standard chain verification |
CCU_TIMEOUT | No | No | Timeout for a CCU JSON-RPC call, in MILLISECONDS |
CCU_SCRIPT_TIMEOUT | No | No | Timeout for HomeMatic Script execution (ReGa), in MILLISECONDS — scripts are slower than plain API calls |
CACHE_TTL | No | No | Lifetime of the on-disk device-type schema cache, in SECONDS |
CCU_RATE_LIMIT_BURST | No | No | Token-bucket burst size for CCU requests — how many may be issued back to back |
CCU_RATE_LIMIT_RATE | No | No | Sustained CCU request rate, in requests per second |
RESOURCE_POLL_INTERVAL | No | No | How often MCP resources are polled for change notifications, in SECONDS |
LOG_LEVEL | No | No | error | warn | info | debug. Logs are structured JSON on stderr |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/claymore666/ccu-mcp |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 1 secret: CCU_PASSWORD |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account claymore666 |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | ccu-mcp@1.11.7 runs nothing at install |
| Code red flags | Pass | Read 81 files in ccu-mcp@1.11.7: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 81 files, including comments and the README |
Popularity & health: 65 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
2 forks, 225 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.claymore666/ccu-mcp |
|---|---|
| Publisher | GitHub account claymore666 |
| How the name is verified | Name verified via GitHub account claymore666. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | npm ccu-mcp 1.11.7 (stdio) |
| Version | 1.11.7 |
| Published | |
| Last updated | |
| Source repository | https://github.com/claymore666/ccu-mcp |
| Website | None linked |
| Category | Files & documents (assigned by keyword rule, not by hand) |
Related servers in Files & documents
- Bitdefender GravityZone4/4MCP server for Bitdefender GravityZone's JSON-RPC API.
AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor4/4Audits any remote agent or MCP URL for JSON-RPC compliance, latency…
- GenPark JSON-RPC Batch Pipelining Dispatcher3/4High-throughput JSON-RPC 2.0 batch pipelining and inter-tool…
MoltNode by Chord8/8Read 31 blockchains over JSON-RPC and swap via Chord: best route,…- openclaw-control-mcp7/7MCP server bridging Claude Code to the OpenClaw gateway management…
- MCP Protocol Conformance7/7MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas,…