Ccu MCP server

Read from the package source without running it. The installed server may list more.

• acknowledge_service_messages

  Confirm/dismiss active service messages (e.g. clear a low-battery or unreachable warning).

• create_system_variablewrite action

  Create a new system variable. Types: 'bool', 'float' (optional min/max/unit),

• delete_system_variablewrite action

  Delete a system variable by name. Use list_system_variables to see existing names.

• describe_device_type

  Get the full channel/datapoint schema for a device type (e.g. 'HmIP-eTRV-2').

• execute_programwrite action

  Trigger an automation program on the CCU. NOT idempotent — will not be auto-retried.

• get_connection_info

  Report which CCU target is currently active — host, user, https, protected/read-only flags, and

• get_paramset

  Read all parameters for a channel: VALUES (runtime state), MASTER (config), or a link

• get_rssi

  Report radio link quality (RSSI, in dBm) for every device, resolved to device names, plus

• get_service_messages

  Get all active service messages (low battery, unreachable, etc.) with device details and timestamps.

• get_system_info

  Get CCU system information: firmware version, serial number, addresses. Reports the active

• get_value

  Read a single datapoint value from a device channel.

• get_values

  Read datapoint values for multiple channels at once via HM Script.

• help

  Context-aware help. No args: conceptual guide.

• list_ccu_targets

  List all configured CCU targets (profiles) you can switch between with use_ccu — name, host,

• list_devices

  List all devices with their channels, types, and addresses.

• list_functions

  List all function groups (Heating, Lighting, etc.) with their assigned channel IDs.

• list_interfaces

  List available communication interfaces (BidCos-RF, HmIP-RF, VirtualDevices, etc.).

• list_links

  List direct device links (Direktverknüpfungen) — sender→receiver channel pairings that operate

• list_programs

  List all automation programs. Use execute_program to trigger them.

• list_rooms

  List all rooms with their assigned channel IDs. Use with list_devices to find devices by room.

• list_system_variables

  List all system variables with current values and metadata. Use set_system_variable to modify them.

• put_paramsetwrite action

  Write multiple parameters at once (e.g. thermostat weekly profile).

• run_scriptwrite action

  Execute arbitrary HomeMatic Script on the CCU.

• set_system_variable

  Set a system variable value. Type is auto-detected — use list_system_variables to see available variables.

• set_value

  Set a single datapoint value on a device channel.

• setup_probe

  Check whether a CCU JSON-RPC API answers at a host. Without port/https the two stock

• setup_status

  Report why the server is in setup mode, which env file it will write, and what that

• setup_test

  Validate the env file end-to-end, like `ccu-mcp doctor`: configuration loads, each

• setup_write_profilewrite action

  Add or update one CCU target in the env file (connection settings only). There is

• use_ccu

  Switch the active CCU target. All subsequent tool calls go to this target until switched again

• Code scan80 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 3 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Ccu: common questions

Is Ccu MCP server safe?

Mostly: it is graded B (83/100). Read the Ccu safety report

How do I install Ccu?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Ccu need an API key?

Yes. The registry entry asks for CCU_PASSWORD.

Is Ccu maintained?

The last commit was 4 days ago (2026-09-16). The latest release is v1.11.1.