MCP Server
MCP
io.github.claymore666/debmatic-mcp
MCP server for controlling HomeMatic smart home devices via the CCU JSON-RPC API
Install
npx -y [email protected]
Configuration Example
{
"remotes": [],
"packages": [
{
"registryType": "npm",
"identifier": "debmatic-mcp",
"version": "1.3.0",
"runtimeHint": "npx",
"transport": {
"type": "stdio"
},
"packageArguments": [
{
"value": "--stdio",
"type": "positional"
}
],
"environmentVariables": [
{
"description": "Hostname or IP of your HomeMatic CCU (debmatic, CCU3, or RaspberryMatic)",
"isRequired": true,
"format": "string",
"name": "CCU_HOST"
},
{
"description": "CCU admin password (same as the WebUI login)",
"isRequired": true,
"format": "string",
"isSecret": true,
"name": "CCU_PASSWORD"
},
{
"description": "CCU username",
"format": "string",
"default": "Admin",
"name": "CCU_USER"
},
{
"description": "Connect to the CCU via HTTPS (self-signed certificates supported)",
"format": "boolean",
"default": "false",
"name": "CCU_HTTPS"
},
{
"description": "CCU API port (80 for HTTP, 443 for HTTPS)",
"format": "number",
"default": "80",
"name": "CCU_PORT"
},
{
"description": "Directory for the device type cache and session persistence",
"format": "string",
"default": "/data",
"name": "CACHE_DIR"
},
{
"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",
"format": "string",
"name": "MCP_ALLOWED_ORIGINS"
},
{
"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",
"format": "string",
"name": "MCP_ALLOWED_HOSTS"
}
]
}
]
}
mcp
model-context-protocol
npm
By
Comments
Sign in to leave a comment