Ha MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with access to Home Assistant, enabling smart home control and automation management. The ha mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

• 40 Specialized Tools — Entity queries, automation CRUD, helper management, scripts, scenes, devices, areas, labels, floors, zones, persons, tags, traces, blueprints, updates, todos, calendars, cameras, dashboards, system log, and more
• Hybrid Architecture — WebSocket for most operations, REST API for automation/script/scene CRUD
• Complete CRUD — Create, read, update, delete automations/scripts/scenes/helpers
• Deep System Access — Query registries, analyze dependencies, access logbook, validate config
• Flexible Output — Natural language (LLM-optimized) and JSON formats
• Access Control — Read-only mode, whitelist/blacklist, fine-grained action-level control

Its toolset

Everything the assistant can do here goes through one of these:

• ha-mcp — Start the MCP server
• Category — Count
• Entity — 5
• Registry — 10
• Automation — 1
• Helpers — 2
• Analysis — 4
• Services — 2
• Logs — 1
• HACS — 1
• Guidance — 1

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ha MCP's toolset — ha-mcp, Category, Entity and 8 more — is a fair guide to whether it matches your workflow. It is maintained by zorak1103; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ha MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ha mcp mcp server does with a few real requests.