Home Assistant MCP Server for VS Code Copilot 15 tools — connect in under 2 minutes
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Home Assistant and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"home-assistant": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
GitHub Copilot Agent mode brings Home Assistant data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 15 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
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 VS Code Copilot 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 VS Code Copilot via MCP
Follow these steps to integrate the Home Assistant MCP Server with VS Code Copilot.
Create MCP config
Create a .vscode/mcp.json file in your project root
Add the server config
Paste the JSON configuration above
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Start using Home Assistant
Ask Copilot: "Using Home Assistant, help me..." — 15 tools available
Why Use VS Code Copilot with the Home Assistant MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Home Assistant through the Model Context Protocol.
VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Home Assistant + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Home Assistant MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Home Assistant MCP Tools for VS Code Copilot (15)
These 15 tools become available when you connect Home Assistant to VS Code Copilot 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 VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot
Common issues when connecting Home Assistant to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Home Assistant + VS Code Copilot FAQ
Common questions about integrating Home Assistant MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.Connect Home Assistant with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Home Assistant to VS Code Copilot
Get your token, paste the configuration, and start using 15 tools in under 2 minutes. No API key management needed.