Want to test the latest changes before the weekly Tuesday release? The dev channel provides early access to features, bug fixes, and improvements as soon as they're merged to master.
Who should use this:
- Contributors testing their PRs
- Issue reporters verifying fixes
- Early adopters wanting the latest features
Important: Dev releases (.devN) may contain bugs. For production use, stick with stable releases.
| Channel | When Updated | Package/Tag |
|---|---|---|
| Dev | Every push to master | ha-mcp-dev / :dev |
| Stable | Weekly (Tuesday 10:00 UTC) | ha-mcp / :latest |
The simplest method - no installation required, no virtual environments, just run:
# Run dev version directly
uvx ha-mcp-devCheck version:
uvx ha-mcp-dev --version
# Output: ha-mcp 6.3.1.dev140Switch back to stable:
uvx ha-mcpConfig changes required: None. Uses the same HOMEASSISTANT_URL and HOMEASSISTANT_TOKEN environment variables.
If you prefer installing the package:
# Install system-wide (requires sudo/admin on some systems)
pip install --user ha-mcp-dev
# Run the installed package
ha-mcp-devCheck version:
pip show ha-mcp-dev | grep VersionSwitch back to stable:
pip uninstall ha-mcp-dev -y
pip install --user ha-mcpUsing uv's package installer:
# Create a virtual environment (one-time setup)
uv venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
# Install dev version
uv pip install ha-mcp-dev
# Run
ha-mcp-devCheck version:
uv pip show ha-mcp-dev | grep VersionSwitch back to stable:
uv pip uninstall ha-mcp-dev
uv pip install ha-mcpDev images are published to GitHub Container Registry with the dev tag.
Pull the dev image:
docker pull ghcr.io/homeassistant-ai/ha-mcp:devRun in stdio mode (Claude Desktop):
docker run --rm -i \
-e HOMEASSISTANT_URL=http://your-ha-instance:8123 \
-e HOMEASSISTANT_TOKEN=your_token \
ghcr.io/homeassistant-ai/ha-mcp:devRun in HTTP mode (web clients):
docker run -d -p 8086:8086 \
-e HOMEASSISTANT_URL=http://your-ha-instance:8123 \
-e HOMEASSISTANT_TOKEN=your_token \
ghcr.io/homeassistant-ai/ha-mcp:dev ha-mcp-webConfig changes required: Change the image tag from latest to dev:
- ghcr.io/homeassistant-ai/ha-mcp:latest
+ ghcr.io/homeassistant-ai/ha-mcp:devSwitch back to stable:
docker pull ghcr.io/homeassistant-ai/ha-mcp:latest
# Stop your dev container and start a new one with :latest tagThe dev channel is available as a separate add-on in the Home Assistant add-on store.
To use the dev channel:
- Open Home Assistant
- Go to Settings → Add-ons → Add-on Store
- Search for "Home Assistant MCP Server (Dev)"
- Click Install
- Configure with your token (if not using auto-discovery)
- Start the add-on
Key differences from stable add-on:
| Property | Stable | Dev |
|---|---|---|
| Name | Home Assistant MCP Server | Home Assistant MCP Server (Dev) |
| Slug | ha_mcp |
ha_mcp_dev |
| Stage | Stable | Experimental |
| Updates | Weekly (Tuesday) | Every master push |
Can I run both? Yes! Both add-ons can be installed simultaneously. They use different slugs and configuration.
Switch back to stable: Simply stop the dev add-on and start/install the stable "Home Assistant MCP Server" add-on instead.
If you're using Claude Desktop, update your claude_desktop_config.json:
Location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
For uvx (dev channel):
{
"mcpServers": {
"ha-mcp": {
"command": "uvx",
"args": ["ha-mcp-dev"],
"env": {
"HOMEASSISTANT_URL": "http://your-ha-instance:8123",
"HOMEASSISTANT_TOKEN": "your_token"
}
}
}
}Config changes required: Change "ha-mcp" to "ha-mcp-dev" in the args array.
Switch back to stable: Change "ha-mcp-dev" back to "ha-mcp" in the args array, then restart Claude Desktop.
The easiest way to check your version:
# With uvx
uvx ha-mcp-dev --version
# With pip
pip show ha-mcp-dev | grep Version
# With uv
uv pip show ha-mcp-dev | grep Version
# With Docker
docker run --rm ghcr.io/homeassistant-ai/ha-mcp:dev ha-mcp --versionDev versions follow the format: 6.3.1.dev140 where .dev140 indicates the 140th commit since the last stable release.
If you encounter issues with a dev release:
- Note the exact version number (e.g.,
6.3.1.dev140) - Check if the issue exists in stable - Try the latest stable release to confirm it's dev-specific
- Report the issue:
- If it's a regression (worked in stable, broken in dev), comment on the related PR or issue
- If it's a new bug, open a bug report and include:
- The dev version number
- Whether it reproduces in stable
- Steps to reproduce