michal/mcpctl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
44838dbe9d9a85b33b5f16dd1c1e09c87b0ea577
mcpctl/templates/home-assistant.yaml

23 lines
759 B
YAML
Raw Normal View History

feat: add MCP healthcheck probes and new templates (grafana, home-assistant, node-red) - Add healthCheck spec to templates and servers (tool, arguments, interval, timeout, failureThreshold) - Add healthStatus, lastHealthCheck, events fields to instances - Create grafana, home-assistant, node-red templates with healthcheck probes - Add healthcheck probes to existing templates (github, slack, postgres, jira) - Show HEALTH column in `get instances` and Events section in `describe instance` - Display healthCheck details in `describe server` and `describe template` - Schema + storage + display only; actual probe runner is future work Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-22 22:48:59 +00:00
name: home-assistant
version: "1.0.0"
description: Home Assistant MCP server for smart home control and entity management
fix: HTTP health probes use container IP for internal network communication mcpd and MCP containers share the mcp-servers Docker network. HTTP probes must use the container's internal IP + containerPort instead of localhost + host-mapped port. Also extracts container IP from Docker inspect. Updated home-assistant template to use ghcr.io/homeassistant-ai/ha-mcp Docker image (SSE transport) instead of broken npm package. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-23 00:52:17 +00:00
dockerImage: "ghcr.io/homeassistant-ai/ha-mcp:latest"
transport: SSE
containerPort: 8086
repositoryUrl: https://github.com/homeassistant-ai/ha-mcp
command:
- python
- -c
- "from ha_mcp.server import HomeAssistantSmartMCPServer; s = HomeAssistantSmartMCPServer(); s.mcp.run(transport='sse', host='0.0.0.0', port=8086)"
feat: add MCP healthcheck probes and new templates (grafana, home-assistant, node-red) - Add healthCheck spec to templates and servers (tool, arguments, interval, timeout, failureThreshold) - Add healthStatus, lastHealthCheck, events fields to instances - Create grafana, home-assistant, node-red templates with healthcheck probes - Add healthcheck probes to existing templates (github, slack, postgres, jira) - Show HEALTH column in `get instances` and Events section in `describe instance` - Display healthCheck details in `describe server` and `describe template` - Schema + storage + display only; actual probe runner is future work Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-22 22:48:59 +00:00
healthCheck:
fix: HTTP health probes use container IP for internal network communication mcpd and MCP containers share the mcp-servers Docker network. HTTP probes must use the container's internal IP + containerPort instead of localhost + host-mapped port. Also extracts container IP from Docker inspect. Updated home-assistant template to use ghcr.io/homeassistant-ai/ha-mcp Docker image (SSE transport) instead of broken npm package. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-23 00:52:17 +00:00
tool: ha_search_entities
arguments:
query: "light"
feat: add MCP healthcheck probes and new templates (grafana, home-assistant, node-red) - Add healthCheck spec to templates and servers (tool, arguments, interval, timeout, failureThreshold) - Add healthStatus, lastHealthCheck, events fields to instances - Create grafana, home-assistant, node-red templates with healthcheck probes - Add healthcheck probes to existing templates (github, slack, postgres, jira) - Show HEALTH column in `get instances` and Events section in `describe instance` - Display healthCheck details in `describe server` and `describe template` - Schema + storage + display only; actual probe runner is future work Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-22 22:48:59 +00:00
env:
fix: HTTP health probes use container IP for internal network communication mcpd and MCP containers share the mcp-servers Docker network. HTTP probes must use the container's internal IP + containerPort instead of localhost + host-mapped port. Also extracts container IP from Docker inspect. Updated home-assistant template to use ghcr.io/homeassistant-ai/ha-mcp Docker image (SSE transport) instead of broken npm package. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-23 00:52:17 +00:00
- name: HOMEASSISTANT_URL
feat: add MCP healthcheck probes and new templates (grafana, home-assistant, node-red) - Add healthCheck spec to templates and servers (tool, arguments, interval, timeout, failureThreshold) - Add healthStatus, lastHealthCheck, events fields to instances - Create grafana, home-assistant, node-red templates with healthcheck probes - Add healthcheck probes to existing templates (github, slack, postgres, jira) - Show HEALTH column in `get instances` and Events section in `describe instance` - Display healthCheck details in `describe server` and `describe template` - Schema + storage + display only; actual probe runner is future work Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-22 22:48:59 +00:00
description: Home Assistant instance URL (e.g. http://homeassistant.local:8123)
required: true
fix: HTTP health probes use container IP for internal network communication mcpd and MCP containers share the mcp-servers Docker network. HTTP probes must use the container's internal IP + containerPort instead of localhost + host-mapped port. Also extracts container IP from Docker inspect. Updated home-assistant template to use ghcr.io/homeassistant-ai/ha-mcp Docker image (SSE transport) instead of broken npm package. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-23 00:52:17 +00:00
- name: HOMEASSISTANT_TOKEN
feat: add MCP healthcheck probes and new templates (grafana, home-assistant, node-red) - Add healthCheck spec to templates and servers (tool, arguments, interval, timeout, failureThreshold) - Add healthStatus, lastHealthCheck, events fields to instances - Create grafana, home-assistant, node-red templates with healthcheck probes - Add healthcheck probes to existing templates (github, slack, postgres, jira) - Show HEALTH column in `get instances` and Events section in `describe instance` - Display healthCheck details in `describe server` and `describe template` - Schema + storage + display only; actual probe runner is future work Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-22 22:48:59 +00:00
description: Home Assistant long-lived access token
required: true
Reference in New Issue Copy Permalink