English Français العربية

io.github.daedalus/mcp-homeassistant

Official registry Other

MCP server exposing Home Assistant REST API functionality

Source code Documentation

What can you do with io.github.daedalus/mcp-homeassistant?

  • get_api_status - Check if the API is running
  • get_config - Get HA configuration
  • get_components - List loaded components
  • get_events - List event types and listener counts
  • get_services - List available services by domain
  • get_states - Get all entity states
  • get_state - Get a specific entity state
  • set_state - Update or create an entity state

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package mcp-homeassistant
Claude Code 
claude mcp add mcp-homeassistant -- uvx mcp-homeassistant==0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcp-homeassistant": {
            "command": "uvx",
            "args": [
                "mcp-homeassistant==0.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-homeassistant
  2. Install
  3. Configuration
  4. Usage
  5. Tools
  6. Resources
  7. Development

mcp-homeassistant

MCP server exposing Home Assistant 2026.4.1 REST API functionality.

mcp-name: io.github.daedalus/mcp-homeassistant

Install

pip install mcp-homeassistant

Configuration

Set the following environment variables:

  • HA_URL: Home Assistant URL (default: http://localhost:8123)
  • HA_TOKEN: Long-Lived Access Token (required)

Usage

export HA_URL="http://homeassistant:8123"
export HA_TOKEN="your_long_lived_access_token"
mcp-homeassistant

Tools

The MCP server exposes the following tools:

  • get_api_status - Check if the API is running
  • get_config - Get HA configuration
  • get_components - List loaded components
  • get_events - List event types and listener counts
  • get_services - List available services by domain
  • get_states - Get all entity states
  • get_state - Get a specific entity state
  • set_state - Update or create an entity state
  • delete_state - Delete an entity state
  • fire_event - Fire a custom event
  • call_service - Call a Home Assistant service
  • render_template - Render a Jinja template
  • get_history - Get historical state changes
  • get_logbook - Get logbook entries
  • check_config - Validate configuration.yaml
  • handle_intent - Handle an intent
  • get_error_log - Get error log
  • get_calendars - List calendar entities
  • get_calendar_events - Get calendar events

Resources

  • homeassistant://config - Current config
  • homeassistant://states - All entity states
  • homeassistant://services - Available services
  • homeassistant://components - Loaded components

Development

git 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/

Frequently asked questions

What is io.github.daedalus/mcp-homeassistant?

MCP server exposing Home Assistant REST API functionality

How do I install io.github.daedalus/mcp-homeassistant?

It runs on your machine. In Claude Code: claude mcp add mcp-homeassistant -- uvx mcp-homeassistant==0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.daedalus/mcp-homeassistant need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.daedalus/mcp-homeassistant open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.daedalus/mcp-homeassistant?

It is published by daedalus. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.