How to Use the Home Assistant MCP in VS Code Copilot

Q: Can VS Code Copilot check my Home Assistant YAML syntax?

Yes, it runs checkhaconfiguration to validate your files against the live instance. The agent will read the error output and suggest fixes inline.

Q: How do we discover available devices on a shared MCP network?

Use listentitystates to dump every active device. It returns the entity IDs, current states, and all attached attributes.

Share live smart home context across your engineering team in VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Home Assistant MCP to VS Code Copilot

Create your Vinkius account to connect Home Assistant to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Home Assistant with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-wide MCP Server integration

`get_ha_config` pulls your installation path, version, and location data directly into VS Code Copilot. You commit your MCP config to the repository, and every developer gets instant access to the shared test environment. Nobody has to manually configure API endpoints or look up documentation. `get_api_status` verifies the remote instance is reachable before anyone starts writing code. Shared development requires consistent testing. If the test server goes down, the agent alerts the developer before they waste time debugging network timeouts.

Read live states and historical logs

`get_entity_state` fetches the exact current condition of any mapped device. When a team member writes a new automation for the office thermostat, the agent reads the actual sensor data to mock the logic. It uses real timestamps to test time-based conditions. `get_entity_history` pulls the state changes over the last 24 hours. Debugging requires historical context. You feed this data into Copilot to identify pattern anomalies, like a motion sensor firing too frequently or a smart plug dropping offline.

Execute services and calendar events

`call_ha_service` sends commands to any domain on the network. You instruct your AI client to test a new script, and it fires the exact payload. The editor acts as a complete control panel for your test environment. `list_ha_calendars` finds all connected schedules, and `get_calendar_events` pulls the upcoming entries. Scheduling automations often involves external calendars. You write logic that reacts to specific meeting titles or busy blocks without leaving your IDE.

Setup guide

Set up Home Assistant MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Home Assistant MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Home Assistant tools listed. Try asking: "List my recent Home Assistant transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "home-assistant-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Home Assistant. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Home Assistant now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Home Assistant MCP in VS Code Copilot

Commit your .vscode/mcp.json file to your Git repository. Every developer who pulls the repo will automatically inherit the server configuration.

Yes, it runs check_ha_configuration to validate your files against the live instance. The agent will read the error output and suggest fixes inline.

It works via the standard protocol. Your IT team manages the API tokens, and developers query the server through the standard chat interface.

Use list_entity_states to dump every active device. It returns the entity IDs, current states, and all attached attributes.

The tool reads internal network IPs, hardware MAC addresses, and physical location coordinates. Vinkius protects this by processing all requests in a stateless memory sandbox. No telemetry is retained, and the execution environment is destroyed the second the query completes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript