MCP server exposing Home Assistant REST API functionality
MCP server exposing Home Assistant 2026.4.1 REST API functionality.
mcp-name: io.github.daedalus/mcp-homeassistant
pip install mcp-homeassistant
Set the following environment variables:
HA_URL: Home Assistant URL (default: http://localhost:8123)HA_TOKEN: Long-Lived Access Token (required)export HA_URL="http://homeassistant:8123"
export HA_TOKEN="your_long_lived_access_token"
mcp-homeassistant
The MCP server exposes the following tools:
get_api_status - Check if the API is runningget_config - Get HA configurationget_components - List loaded componentsget_events - List event types and listener countsget_services - List available services by domainget_states - Get all entity statesget_state - Get a specific entity stateset_state - Update or create an entity statedelete_state - Delete an entity statefire_event - Fire a custom eventcall_service - Call a Home Assistant servicerender_template - Render a Jinja templateget_history - Get historical state changesget_logbook - Get logbook entriescheck_config - Validate configuration.yamlhandle_intent - Handle an intentget_error_log - Get error logget_calendars - List calendar entitiesget_calendar_events - Get calendar eventshomeassistant://config - Current confighomeassistant://states - All entity stateshomeassistant://services - Available serviceshomeassistant://components - Loaded componentsgit clone https://github.com/daedalus/mcp-homeassistant.git
cd mcp-homeassistant
pip install -e ".[test]"
# run tests
pytest
# format
ruff format src/ tests/
# lint
ruff check src/ tests/
# type check
mypy src/
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx mcp-homeassistantMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-daedalus-mcp-homeassistant": {
"command": "uvx",
"args": [
"mcp-homeassistant"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemcp-homeassistantpypiio.github.daedalus/mcp-homeassistant works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.