2,500+ MCP servers ready to use
Vinkius

Home Assistant MCP Server for Google ADK 15 tools — connect in under 2 minutes

Built by Vinkius GDPR 15 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Home Assistant as an MCP tool provider through the Vinkius and your ADK agents can call every tool with full schema introspection.

Vinkius supports streamable HTTP and SSE.

python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token — get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="home_assistant_agent",
    instruction=(
        "You help users interact with Home Assistant "
        "using 15 available tools."
    ),
    tools=[mcp_tools],
)
Home Assistant
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.

Google ADK natively supports Home Assistant as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 15 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

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 Google ADK 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 Google ADK via MCP

Follow these steps to integrate the Home Assistant MCP Server with Google ADK.

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 15 tools from Home Assistant via MCP

Why Use Google ADK with the Home Assistant MCP Server

Google ADK provides unique advantages when paired with Home Assistant through the Model Context Protocol.

01

Google ADK natively supports MCP tool servers — declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Home Assistant

03

Production-ready features like session management, evaluation, and deployment come built-in — not bolted on

04

Seamless integration with Google Cloud services means you can combine Home Assistant tools with BigQuery, Vertex AI, and Cloud Functions

Home Assistant + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Home Assistant MCP Server delivers measurable value.

01

Enterprise data agents: ADK agents query Home Assistant and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Home Assistant tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Home Assistant regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Home Assistant

Home Assistant MCP Tools for Google ADK (15)

These 15 tools become available when you connect Home Assistant to Google ADK via MCP:

01

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

02

check_ha_configuration

Check Home Assistant configuration validity

03

fire_ha_event

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

04

get_api_status

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

05

get_calendar_events

Get events from a Home Assistant calendar

06

get_entity_history

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

07

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

08

get_ha_config

Get the Home Assistant configuration details

09

get_logbook_entries

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

10

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

11

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

12

list_ha_calendars

List all calendars configured in Home Assistant

13

list_ha_components

List all loaded components/integrations in Home Assistant

14

list_ha_events

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

15

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 Google ADK

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

01

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

02

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

03

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

Troubleshooting Home Assistant MCP Server with Google ADK

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

01

McpToolset not found

Update: pip install --upgrade google-adk

Home Assistant + Google ADK FAQ

Common questions about integrating Home Assistant MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Connect Home Assistant to Google ADK

Get your token, paste the configuration, and start using 15 tools in under 2 minutes. No API key management needed.