sport | Started by default | |---|---|---| | `deconz-mcp` | `server` (SSE + Streamable HTTP) on port 8000 | Yes | | `deconz-mcp-stdio` | `stdio` | No — requires `--profile stdio` | ```bash # 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: ```json { "mcpServers": { "deconz": { "command": "docker", "args": ["compose", "-f", "/path/to/docs/docker-compose.yml", "--profile", "stdio", "run", "--rm", "deconz-mcp-stdio"], "env": { "DECONZ_HOST": "192.168.1.10", "DECONZ_API_KEY": "your-api-key-here" } } } } ``` --- ## Kubernetes The manifest at [`k8s/deployment.yaml`](k8s/deployment.yaml) contains all resources needed to run the server in a cluster: | Resource | Purpose | |---|---| | `Namespace` | `deconz-mcp` — isolates all resources | | `Secret` | `DECONZ_API_KEY` and `MCP_AUTH_TOKEN` (base64-encoded) | | `ConfigMap` | `DECONZ_HOST`, `DECONZ_PORT`, `DECONZ_TLS`, `MCP_BASE_URL` | | `Deployment` | 1 replica, non-root, read-only root FS, resource limits | | `Service` | `ClusterIP` on port 80 → pod 8000 | | `Ingress` | Commented-out template for nginx / cert-manager | ### Deploy ```bash # 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 ``` ### Health check ```bash kubectl -n deconz-mcp port-forward svc/deconz-mcp 8000:80 curl http://localhost:8000/health # {"status": "ok", "deconz_configured": true} ``` The `Deployment` configures both a liveness probe and a readiness probe against `/health`, so Kubernetes automatically restarts the pod if the server becomes unresponsive. ### Ingress (optional) Uncomment the `Ingress` section at the bottom of `k8s/deployment.yaml` and set your hostname. TLS termination happens at the ingress controller; the pod always speaks plain HTTP internally. --- ## Health check HTTP transports expose a liveness probe: ```bash curl http://localhost:8080/health # {"status": "ok", "deconz_configured": true} ``` --- ## Project structure ``` 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 ``` --- ## deCONZ API overview The server covers these API categories: | Category | Endpoints | |---|---| | Config | `GET /config`, `PUT /config` (permit join) | | Lights | `GET /lights`, `GET /lights/`, `PUT /lights//state`, `DELETE /lights/` | | Groups | `GET /groups`, `POST /groups`, `PUT /groups//action`, `DELETE /groups/` | | Scenes | Full CRUD under `/groups//scenes/` incl. recall and store | | Sensors | `GET /sensors`, `PUT /sensors//config`, `DELETE /sensors/` | | Rules | Full CRUD under `/rules/` | | Schedules | Full CRUD under `/schedules/` | | Touchlink | `POST /touchlink/scan`,

Mcp Server For Deconz Server

评论

服务器配置