Slhad Aha MCP

What slhad-aha-mcp does

The slhad-aha-mcp MCP server bridges Home Assistant with MCP-compatible clients. It exposes Home Assistant operations as MCP tools, allowing an agent to inspect entities, update their states, invoke services, and manage automation definitions.

Supported areas include lights, sensors, switches, and other Home Assistant entities. The server can search for entities by prefix or regular expression, retrieve entity sources, and access entity and device registry information. Automation tools cover listing, creation, updates, deletion, validation, and tracing.

Additional tools support Lovelace dashboard access and updates, Home Assistant configuration validation, and helpers for creating and managing config-entry integration flows. The repository documentation reports 39 available tools, although the exact tool set may change with the implementation.

How it works

The server uses a Home Assistant URL and a long-lived access token to communicate with the Home Assistant instance. An MCP client can launch it over standard input and output, or connect to a separately running endpoint through SSE or streamable HTTP.

With stdio, the MCP client starts the process and passes configuration through environment variables. For SSE and HTTP, the server runs independently and the client connects to /sse or /mcp respectively. Docker and Podman usage is supported, including a published container image referenced by the installation examples.

The slhad-aha-mcp MCP server can expose resources as tools when configured to do so. Tool definitions consume context-window tokens, and the README specifically warns that some large tools, including Lovelace configuration updates, can use thousands of tokens. Exclude tools that are not needed when the client supports tool filtering.

Setup and configuration

Set HASS_URL to the address of the Home Assistant instance and HASS_ACCESS_TOKEN to a valid long-lived access token. These values are used in stdio, SSE, HTTP, and container examples.

Optional settings shown in the documentation include TRANSPORT, RESOURCES_TO_TOOLS, LIMIT_RESOURCES, and DEBUG. The default transport is stdio. Set the transport and other options according to the process or container startup method being used.

For local development, the repository provides npm scripts for starting SSE and streamable HTTP servers. Example client endpoints are http://localhost:8081/sse for SSE and http://localhost:8081/mcp for streamable HTTP. VS Code and Cursor installation links are included in the README, and a Smithery listing is also provided.

Tools and capabilities

• Query, search, and update Home Assistant entities
• Call Home Assistant services such as device on/off actions
• List, create, update, delete, validate, and trace automations
• Read entity and device registries
• Access and update Lovelace dashboards
• Validate Home Assistant configuration
• Manage config-entry integration flows

The slhad-aha-mcp MCP server is suited to assistants that need both read and write access to a Home Assistant installation. Because several tools can change device state or configuration, client-side approval controls should be configured where available.