Connecting an AI to Hearth

Hearth exposes a remote MCP (Model Context Protocol) connector protected by OAuth 2.1. Any MCP-capable client can use it. Your connector URL is shown in the dashboard under AI clients; it looks like https://<your-hearth>/mcp.

What the AI can do

Exactly what you switched on, under Settings → Devices & services → Hearth AI → Configure. Reading and authoring are on by default; everything that acts on your home is off until you enable it.

• Read areas, entities, states, and the service catalog — and only entities you exposed to Assist.
• Create, validate, edit, and delete automations, scenes, and scripts, the same way the Home Assistant UI editor does.
• If you enable it: operate your devices, activate scenes, and run scripts.
• If you enable it: walk through adding a new integration — though Hearth refuses to relay a password, API key, or token, and hands those steps back to you.

What it can never do

Touch cameras, locks, alarms, or location entities — not directly, and not by writing them into an automation, scene, or script. It can never fire an automation. Host-level services such as shell_command, hassio, and homeassistant.restart are refused.

This is enforced twice: in Hearth and inside the integration running on your own Home Assistant, so neither one is the only guard.

Claude

claude.ai → Settings → Connectors → Add custom connector → paste the URL → Connect. Claude Code: claude mcp add --transport http hearth <url>.

ChatGPT

Requires Plus, Pro, Business, Enterprise, or Edu. Settings → Apps & Connectors → Advanced → Developer mode → create a connector with OAuth authentication.

Gemini

Gemini CLI supports remote MCP servers on every account: gemini mcp add --transport http hearth <url>. The Gemini app supports custom MCP servers only inside Gemini Spark (AI Pro/Ultra, US). Treat Gemini support as beta.

Managed AI

Prefer not to bring your own AI? The Managed plan runs Claude for you and answers inside Home Assistant's Assist as the Hearth AI conversation agent.