LiveKit Agent Integrated With Home Assistant MCP Server

LiveKit Agent integrated with MCP server of Home Assistant. The livekit agent integrated with home assistant mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

The dashboard UI is a Home Assistant custom integration + Lovelace card that runs the session inside HA: ha-livekit-agent-frontend. Run this worker, install that integration, point both at the same LiveKit project, and you're set.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

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

• Cost-aware — STT is billed continuously, so it follows the mic: enabled while audio
• Variable — Purpose
• HA_URL — Home Assistant base URL. /api/mcp is appended automatically
• HA_TOKEN — Home Assistant long-lived access token (sent as a bearer token)
• AGENT_NAME — Explicit-dispatch worker name (default ha-agent). Must match the integration's Agent name
• STT_IDLE_TIMEOUT — Seconds after the mic is gated before STT is torn down to save cost (default 120)

Configuration

You will need 6 environment variables: LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET, LIVEKIT_INFERENCE_URL, LIVEKIT_INFERENCE_API_KEY, LIVEKIT_INFERENCE_API_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Home Assistant with the MCP Server integration enabled, and a long-lived access token. - A LiveKit server (self-hosted or LiveKit Cloud) for the realtime transport. - LiveKit Inference credentials for STT/LLM/TTS (LiveKit Cloud). - The HA integration installed for the dashboard UI.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the livekit agent integrated with home assistant mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. LiveKit Agent Integrated With Home Assistant's toolset — Cost-aware, Variable, HA_URL and 3 more — is a fair guide to whether it matches your workflow. It is maintained by longcw; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.