io.github.claymore666/ccu-mcp
io.github.claymore666/ccu-mcp
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
Connect this server
Add this to your MCP client config — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor).Suits: Claude Desktop · Cursor.
{
"mcpServers": {
"ccu-mcp": {
"command": "npx",
"args": [
"-y",
"ccu-mcp@1.11.7"
],
"env": {
"CCU_HOST": "<your CCU_HOST>",
"CCU_PASSWORD": "<your CCU_PASSWORD>",
"CCU_USER": "Admin",
"CCU_HTTPS": "false",
"CCU_PORT": "80",
"CACHE_DIR": "/data",
"CCU_TLS_VERIFY": "false",
"CCU_TIMEOUT": "10000",
"CCU_SCRIPT_TIMEOUT": "30000",
"CACHE_TTL": "86400",
"CCU_RATE_LIMIT_BURST": "20",
"CCU_RATE_LIMIT_RATE": "10",
"RESOURCE_POLL_INTERVAL": "60",
"LOG_LEVEL": "info"
}
}
}
}- CCU_HOSTrequiredHostname or IP of your HomeMatic CCU (debmatic, CCU3, or OpenCCU/RaspberryMatic)
- CCU_PASSWORDrequiredsecretCCU admin password (same as the WebUI login). Must be set; the value may be empty for a CCU with no password
- CCU_USERCCU username
- CCU_HTTPSConnect to the CCU via HTTPS (self-signed certificates supported)
- CCU_PORTCCU API port (80 for HTTP, 443 for HTTPS)
- CACHE_DIRDirectory for the device type cache and session persistence
- CCU_TLS_VERIFYVerify 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_TIMEOUTTimeout for a CCU JSON-RPC call, in MILLISECONDS
- CCU_SCRIPT_TIMEOUTTimeout for HomeMatic Script execution (ReGa), in MILLISECONDS — scripts are slower than plain API calls
- CACHE_TTLLifetime of the on-disk device-type schema cache, in SECONDS
- CCU_RATE_LIMIT_BURSTToken-bucket burst size for CCU requests — how many may be issued back to back
- CCU_RATE_LIMIT_RATESustained CCU request rate, in requests per second
- RESOURCE_POLL_INTERVALHow often MCP resources are polled for change notifications, in SECONDS
- LOG_LEVELerror | warn | info | debug. Logs are structured JSON on stderr
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Developer Tools
- Version
- 1.11.7
- Registry
- active
- Published
- 10/25/2026
More Developer Tools servers
Browse all Developer Tools →io.github.claymore666/debmatic-mcp
claymore666
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
Clay Seal
clayseal
Authorizes MCP tool calls against a session policy, not one call at a time.
io.github.claytono/go-unifi-mcp
claytono
Manage UniFi sites, devices, clients, networks, port forwarding, DNS, and firewall
Clean
cleanmcp
Clean finds your next customers: ICP, researched leads, replies and sequences, from any agent.
CleanSlice
CleanSlice
Architecture docs and patterns for NestJS + Nuxt full-stack apps
Clean Yield Data Tools
cleanyield-data
Company enrichment, FMCSA carriers, app reviews, live ATS jobs and LatAm public tenders, via Apify.
Add the badge to your site
Show visitors that io.github.claymore666/ccu-mcp is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-claymore666-ccu-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="io.github.claymore666/ccu-mcp — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/io-github-claymore666-ccu-mcp?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.