Server facts
debmatic-mcp
Project
- Author
- claymore666
- Repository
- github.com/claymore666/debmatic-mcp
- License
- Not specified
- Category
- Mobile & Desktop Automation
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 9
- Last commit
- Data as of
Tags
- Smart Home
- ccu
- debmatic
- eq3
- home automation
- homematic
- homematic ip
- iot
- mcp
- raspberrymatic
Overview
HomeMatic heating, sensors, and automation programs become accessible from Claude, Cursor, and other MCP clients through a local CCU connection. The project supports debmatic, CCU3, and OpenCCU using the CCU’s JSON-RPC interface. A typical workflow starts by discovering devices and narrowing results by room, function, type, or name. Device schemas then identify available datapoints, their permitted ranges, and supported operations. Users can inspect individual readings or retrieve values across several channels, including selections organized by room or function.
Control tools cover individual datapoint changes, parameter batches such as thermostat schedules, system-variable updates, and program execution. Single-value writes return the prior setting, while interface selection and value types are resolved automatically. Service-message inspection surfaces battery and reachability issues alongside device details and timestamps. Additional tools expose communication interfaces, CCU information, and contextual guidance. For tasks outside the dedicated tools, users can execute HomeMatic Script; script execution and program triggers are not automatically retried. Deployment options include a client-launched stdio process or a standalone Docker HTTP service with bearer-token authentication.
debmatic-mcp setup notes
- debmatic-mcp records stdio only; confirm a network transport upstream before planning remote access.
- debmatic-mcp has no recorded license; confirm reuse terms in its repository.