What Home Assistant URL should I use?

For local instances, use your Home Assistant's local network URL: `http://YOUR_IP:8123` (or `http://homeassistant.local:8123`). For cloud access via Nabu Casa, use your remote URL: `https://YOUR_INSTANCE.ui.nabu.casa`. The API is accessible at the same base URL as your Home Assistant frontend.

How do I get a Long-Lived Access Token?

Log in to your Home Assistant web interface, go to your user profile (click your name in the sidebar, then **Profile**), scroll down to **Long-Lived Access Tokens**, click **Create Token**, give it a name (e.g., 'MCP Server'), and copy the generated token. This token never expires unless manually revoked.

What devices and integrations are supported?

All Home Assistant integrations are supported since the API works at the service/state level. This includes lights (Philips Hue, LIFX, etc.), thermostats (Nest, Ecobee, etc.), covers/blinds, switches, media players (Sonos, Chromecast, etc.), sensors, cameras, locks, vacuums, and 1000+ other integrations. Use `list_entity_states` to discover all available entities.

Can I trigger Home Assistant automations from the API?

Yes! You can trigger automations in multiple ways: 1) Call the `automation.trigger` service directly, 2) Fire a custom event using `fire_ha_event` that matches an event trigger in your automation, 3) Call the `script.turn_on` service to run scripts. You can also control devices directly which will trigger related automations.

Home Assistant MCP Server for Pydantic AI 15 tools — connect in under 2 minutes

Name: Home Assistant
Availability: InStock
Author: Vinkius

ai.pydantic.dev/mcp

Built by Vinkius GDPR 15 Tools SDK

Pydantic AI brings type-safe agent development to Python with first-class MCP support. Connect Home Assistant through the Vinkius and every tool is automatically validated against Pydantic schemas — catch errors at build time, not in production.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerHTTP

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    server = MCPServerHTTP(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

    agent = Agent(
        model="openai:gpt-4o",
        mcp_servers=[server],
        system_prompt=(
            "You are an assistant with access to Home Assistant "
            "(15 tools)."
        ),
    )

    result = await agent.run(
        "What tools are available in Home Assistant?"
    )
    print(result.data)

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Home Assistant MCP Server

Connect to your Home Assistant instance (local or Nabu Casa cloud) and control your entire smart home from any AI agent. Manage lights, climate, media players, covers, switches, and trigger automations via the Home Assistant REST API.

Pydantic AI validates every Home Assistant tool response against typed schemas, catching data inconsistencies at build time. Connect 15 tools through the Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code — full type safety, structured output guarantees, and dependency injection for testable agents.

What you can do

Entity Discovery — List all entities and their current states across all integrations
Device Control — Turn lights on/off, adjust brightness, set thermostat temperatures, open/close covers
Service Calls — Call any Home Assistant service (light, switch, climate, cover, media_player, automation, script)
State Monitoring — Get real-time state of any entity including sensors, binary sensors, and device trackers
History & Logbook — Query historical state changes and logbook entries for analysis
Calendar Management — List and query calendar events from Home Assistant calendars
Event Automation — Fire custom events to trigger Home Assistant automations
Template Rendering — Render Jinja2 templates for advanced state access
Configuration — View system configuration, loaded components, and validate configuration
Local or Cloud — Works with local instances (http://IP:8123) or Nabu Casa cloud (https://INSTANCE.ui.nabu.casa)

The Home Assistant MCP Server exposes 15 tools through the Vinkius. Connect it to Pydantic AI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Home Assistant to Pydantic AI via MCP

Follow these steps to integrate the Home Assistant MCP Server with Pydantic AI.

Install Pydantic AI

Run pip install pydantic-ai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 15 tools from Home Assistant with type-safe schemas

Why Use Pydantic AI with the Home Assistant MCP Server

Pydantic AI provides unique advantages when paired with Home Assistant through the Model Context Protocol.

Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application

Model-agnostic architecture — switch between OpenAI, Anthropic, or Gemini without changing your Home Assistant integration code

Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors

Dependency injection system cleanly separates your Home Assistant connection logic from agent behavior for testable, maintainable code

Home Assistant + Pydantic AI Use Cases

Practical scenarios where Pydantic AI combined with the Home Assistant MCP Server delivers measurable value.

Type-safe data pipelines: query Home Assistant with guaranteed response schemas, feeding validated data into downstream processing

API orchestration: chain multiple Home Assistant tool calls with Pydantic validation at each step to ensure data integrity end-to-end

Production monitoring: build validated alert agents that query Home Assistant and output structured, schema-compliant notifications

Testing and QA: use Pydantic AI's dependency injection to mock Home Assistant responses and write comprehensive agent tests

Home Assistant MCP Tools for Pydantic AI (15)

These 15 tools become available when you connect Home Assistant to Pydantic AI via MCP:

call_ha_service

This is the primary way to control devices in Home Assistant. COMMON SERVICE CALLS: - light.turn_on: entity_id, brightness (0-255), color_temp, rgb_color - light.turn_off: entity_id - switch.turn_on: entity_id - switch.turn_off: entity_id - climate.set_temperature: entity_id, temperature - climate.set_hvac_mode: entity_id, hvac_mode (heat, cool, auto, off) - cover.open_cover: entity_id - cover.close_cover: entity_id - media_player.turn_on: entity_id - media_player.turn_off: entity_id - media_player.media_play: entity_id - automation.trigger: entity_id - script.turn_on: entity_id DOMAINS: light, switch, climate, cover, fan, lock, media_player, automation, script, scene, input_boolean, input_number, notify PARAMETERS: - domain (REQUIRED): Domain name (e.g. light, switch, climate) - service (REQUIRED): Service name (e.g. turn_on, turn_off, set_temperature) - service_data (OPTIONAL): JSON object with service parameters including entity_id EXAMPLES: - "Turn on living room light" → domain="light", service="turn_on", service_data={"entity_id":"light.living_room"} - "Set bedroom temperature to 20" → domain="climate", service="set_temperature", service_data={"entity_id":"climate.bedroom","temperature":20} Call a Home Assistant service on a domain

check_ha_configuration

Check Home Assistant configuration validity

fire_ha_event

The event type must match automation triggers configured in Home Assistant. Fire a custom event in Home Assistant

get_api_status

Use this as a connectivity test before making other API calls. Check if the Home Assistant API is running

get_calendar_events

Get events from a Home Assistant calendar

get_entity_history

Useful for analyzing trends and past behavior. Get historical state data for an entity

get_entity_state

Use entity IDs from list_entity_states (e.g., light.living_room, climate.bedroom, sensor.temperature). Get the current state of a specific entity

get_ha_config

Get the Home Assistant configuration details

get_logbook_entries

Can be filtered by entity and time range. Get Home Assistant logbook entries

list_available_services

g., light: turn_on, turn_off, toggle; climate: set_temperature, set_hvac_mode). Essential for discovering what actions can be performed. List all available services across all domains

list_entity_states

Each entity includes entity_id, state, last_changed timestamp, and attributes. Essential for discovering available devices. List all entity states in Home Assistant

list_ha_calendars

List all calendars configured in Home Assistant

list_ha_components

List all loaded components/integrations in Home Assistant

list_ha_events

Useful for understanding what events Home Assistant is tracking. List all event types currently registered in Home Assistant

render_ha_template

Useful for accessing HA template functions and state from the API. Render a Jinja2 template in Home Assistant

Example Prompts for Home Assistant in Pydantic AI

Ready-to-use prompts you can give your Pydantic AI agent to start working with Home Assistant immediately.

"List all my smart home entities and show me the lights."

"Turn on the living room light and set it to 50% brightness."

"What is the current temperature in the bedroom and what mode is the thermostat?"

Troubleshooting Home Assistant MCP Server with Pydantic AI

Common issues when connecting Home Assistant to Pydantic AI through the Vinkius, and how to resolve them.

MCPServerHTTP not found

Update: pip install --upgrade pydantic-ai

Home Assistant + Pydantic AI FAQ

Common questions about integrating Home Assistant MCP Server with Pydantic AI.

How does Pydantic AI discover MCP tools?

Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.

Does Pydantic AI validate MCP tool responses?

Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.

Can I switch LLM providers without changing MCP code?

Absolutely. Pydantic AI abstracts the model layer — your Home Assistant MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.