deConz MCP

Supportsstdio,SSE, andStreamable HTTPtransports. HTTP transports are protected by a configurablebearer token.

# Clone the repository git clone https://github.com/your-org/deconz-mcp.git cd deconz-mcp # Install with uv (creates an isolated virtual environment) uv sync # Or install with pip into your environment pip install -e .

- Open thePhoscon Appin your browser (usuallyhttp://<gateway-ip>/pwa).
- Go toMenu → Settings → Gateway → Advanced.
- ClickAuthenticate app— this opens the network for 60 seconds.
- Within those 60 seconds, run:

curl -s -X POST http://<gateway-ip>/api \ -H "Content-Type: application/json" \ -d '{"devicetype": "deconz-mcp"}'

# Copy and edit the environment file cp .env.example .env # set DECONZ_HOST, DECONZ_API_KEY, MCP_AUTH_TOKEN # Start the HTTP server docker compose -f docs/docker-compose.yml up # Run a one-shot stdio session docker compose -f docs/docker-compose.yml --profile stdio run --rm deconz-mcp-stdio

Use the stdio service in Claude Desktop:

# 1. Encode your secrets echo -n 'your-api-key' | base64 # → paste into Secret.DECONZ_API_KEY echo -n 'your-mcp-token' | base64 # → paste into Secret.MCP_AUTH_TOKEN # 2. Edit the ConfigMap (DECONZ_HOST, MCP_BASE_URL) in k8s/deployment.yaml # 3. Apply kubectl apply -f k8s/deployment.yaml # 4. Verify kubectl -n deconz-mcp get pods kubectl -n deconz-mcp logs -f deploy/deconz-mcp

kubectl -n deconz-mcp port-forward svc/deconz-mcp 8000:80 curl http://localhost:8000/health # {"status": "ok", "deconz_configured": true}

TheDeploymentconfigures both a liveness probe and a readiness probe against/health, so Kubernetes automatically restarts the pod if the server becomes unresponsive.

Uncomment theIngresssection at the bottom ofk8s/deployment.yamland set your hostname. TLS termination happens at the ingress controller; the pod always speaks plain HTTP internally.

HTTP transports expose a liveness probe:

curl http://localhost:8080/health # {"status": "ok", "deconz_configured": true}

deConz-mcp/ ├── Dockerfile # Multi-stage image build ├── pyproject.toml # Package metadata and dependencies ├── uv.lock # Locked dependency versions ├── README.md ├── docs/ │ └── docker-compose.yml # Compose services (HTTP + stdio) ├── k8s/ │ └── deployment.yaml # Kubernetes: Namespace, Secret, ConfigMap, │ # Deployment, Service, Ingress (template) └── src/ └── deconz_mcp/ ├── __init__.py ├── __main__.py # CLI entrypoint and transport wiring ├── client.py # Async deCONZ REST API HTTP client └── server.py # FastMCP server: tools, resources, prompts

Preliminary assessment only — not legal advice.See full notes below.

When this server runs in a private household and is accessed only by the residents, processing of smart-home device data is likely covered by thehousehold exemption(GDPR Recital 18). In that scenario the GDPR does not apply and no additional compliance steps are required.

Deploying this server in offices, rental properties, hotels, co-working spaces, or any environment where you process data on behalf of other peopletakes you outside the household exemption. In those cases:

- Presence and motion sensor dataconstitutes personal behavioral data (Art. 4(1) GDPR). Establish a documented lawful basis (Art. 6) before processing it.
- Conduct aData Protection Impact Assessment(Art. 35) if the deployment involves systematic monitoring of occupants on a large scale.
- Provide aprivacy noticeto data subjects describing what is collected, for how long, and under what legal basis.

- No data is sent to third parties, analytics services, or cloud providers.
- No telemetry, tracking pixels, or consent libraries are present in this codebase.
- All communication stays between the MCP client, this server, and the local deCONZ gateway.

This GDPR assessment was generated as a preliminary, exploratory evaluation. It does not constitute legal advice and does not replace a legal audit. For binding guidance, consult a qualified data protection lawyer in your jurisdiction.

This software is not affiliated with or endorsed by Dresden Elektronik. Use at your own risk. It does not come with any warranty of any kind. There is no liability for the developer. This software is a personal project that I maintain in my free time. Refer to the licence for more information.

MCP server for managing OpenSprinkler controller via Claude Desktop or any MCP-compatible client.

Connects to a Coreflux MQTT broker, offering tools for Coreflux commands and integration with AI assistants.

An MCP server that connects to a Coreflux MQTT broker, providing Coreflux and MQTT actions as tools for AI assistants.

A free, private, and secure remote MCP server for Home Assistant.

MCP server for Azure IoT Hub - device registry, twins, direct methods, jobs, messaging

MCP server for Google Cast — discover devices, play media, control volume, launch apps, and manage queues over stdio

Home automation you can just talk to. No dashboards, no app to learn.

A safe-by-default MCP server that exposes your Control4 home automation (lights, scenes, locks, thermostats, and media) as structured tools over HTTP and Claude Desktop STDIO for reliable AI-powered control on your local network.

Control and query the status of Ecovacs cleaning robots using the MCP protocol.