AgentHubAgentHub

ccu MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.claymore666/ccu-mcp · v1.11.3

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

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API ccu-mcp is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Required
Requiredsecret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Setup tutorial

  1. Open the ccu-mcp page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add ccu-mcp --env CCU_HOST=<CCU_HOST> --env CCU_PASSWORD=<CCU_PASSWORD> -- npx -y ccu-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "ccu-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ccu-mcp"
      ],
      "env": {
        "CCU_HOST": "<CCU_HOST>",
        "CCU_PASSWORD": "<CCU_PASSWORD>"
      }
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for ccu-mcp

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for ccu-mcp?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

ccu-mcp requires environment variables (CCU_HOST、CCU_PASSWORD). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "CCU_HOST": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

ccu-mcp Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: ccu_mcpExecute the core tool interface of ccu-mcp
Request ArgumentsJSON Schema
{
  "target": "ccu-mcp",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

ccu-mcp + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: ccu-mcp
HTML
<a href="https://myagenthub.cn/p/io.github.claymore666/ccu-mcp" title="Listed on AgentHub: ccu-mcp" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.claymore666/ccu-mcp?lang=en" alt="Listed on AgentHub: ccu-mcp" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: ccu-mcp](https://myagenthub.cn/badge/io.github.claymore666/ccu-mcp?lang=en)](https://myagenthub.cn/p/io.github.claymore666/ccu-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.claymore666/ccu-mcp",
  "type": "mcp-server",
  "version": "1.11.3",
  "displayName": "ccu-mcp",
  "description": "MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API",
  "repository": {
    "url": "https://github.com/claymore666/ccu-mcp",
    "source": "github"
  },
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "ccu-mcp",
        "version": "1.11.3",
        "runtimeHint": "npx",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "CCU_HOST",
            "description": "Hostname or IP of your HomeMatic CCU (debmatic, CCU3, or OpenCCU/RaspberryMatic)",
            "isRequired": true
          },
          {
            "name": "CCU_PASSWORD",
            "description": "CCU admin password (same as the WebUI login). Must be set; the value may be empty for a CCU with no password",
            "isRequired": true,
            "isSecret": true
          },
          {
            "name": "CCU_USER",
            "description": "CCU username"
          },
          {
            "name": "CCU_HTTPS",
            "description": "Connect to the CCU via HTTPS (self-signed certificates supported)"
          },
          {
            "name": "CCU_PORT",
            "description": "CCU API port (80 for HTTP, 443 for HTTPS)"
          },
          {
            "name": "CACHE_DIR",
            "description": "Directory for the device type cache and session persistence"
          },
          {
            "name": "MCP_ALLOWED_ORIGINS",
            "description": "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"
          },
          {
            "name": "MCP_ALLOWED_HOSTS",
            "description": "Extra Host header values accepted by DNS-rebinding protection (comma-separated host:port); add your hostname when behind a proxy or container DNS name"
          },
          {
            "name": "CCU_PROFILES",
            "description": "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"
          },
          {
            "name": "CCU_DEFAULT_PROFILE",
            "description": "Which profile from CCU_PROFILES is active at startup (default: the first listed)"
          },
          {
            "name": "CCU_TLS_VERIFY",
            "description": "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"
          },
          {
            "name": "CCU_TLS_FINGERPRINT",
            "description": "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"
          },
          {
            "name": "CCU_CA_CERT",
            "description": "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"
          },
          {
            "name": "CCU_TIMEOUT",
            "description": "Timeout for a CCU JSON-RPC call, in MILLISECONDS"
          },
          {
            "name": "CCU_SCRIPT_TIMEOUT",
            "description": "Timeout for HomeMatic Script execution (ReGa), in MILLISECONDS — scripts are slower than plain API calls"
          },
          {
            "name": "CACHE_TTL",
            "description": "Lifetime of the on-disk device-type schema cache, in SECONDS"
          },
          {
            "name": "CCU_RATE_LIMIT_BURST",
            "description": "Token-bucket burst size for CCU requests — how many may be issued back to back"
          },
          {
            "name": "CCU_RATE_LIMIT_RATE",
            "description": "Sustained CCU request rate, in requests per second"
          },
          {
            "name": "RESOURCE_POLL_INTERVAL",
            "description": "How often MCP resources are polled for change notifications, in SECONDS"
          },
          {
            "name": "LOG_LEVEL",
            "description": "error | warn | info | debug. Logs are structured JSON on stderr"
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.claymore666/ccu-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.claymore666%2Fccu-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}