This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/mvoska on 2025-03-16 18:44:53+00:00.

Looks like I’m the second one who took this weekend to build a Home Assistant MCP server

I wanted to expose my Home Assistant instance to Claude Code / Cursor so when I was editing my home assistant config folder, it had the context of my entities, devices, etc.

Why build a new MCP server?

1. I couldn’t get the built in MCP server working (via MCP Proxy or from running the inspector)
2. I thought it would be more reliable by connecting directly to the HASS API instead of going through the assist flow.
3. None of the existing MCP servers I could find worked.

Overview:

• Entity Management: Get states, control devices, and search for entities
• Domain Summaries: Get high-level information about entity types
• Automation Support: List and control automations
• Guided Conversations: Use prompts for common tasks like creating automations
• Smart Search: Find entities by name, type, or state
• Token Efficiency: Lean JSON responses to minimize token usage

Tools

• get_version: Get the Home Assistant version
• get_entity: Get the state of a specific entity
• entity_action: Perform actions on entities (turn on, off, toggle)
• list_entities: Get a list of entities with optional filtering
• search_entities_tool: Search for entities matching a query
• domain_summary_tool: Get a summary of a domain’s entities
• list_automations: Get a list of all automations
• call_service_tool: Call any Home Assistant service
• restart_ha: Restart Home Assistant
• get_history: Get the state history of an entity
• get_error_log: Get the Home Assistant error log

Prompts

• create_automation: Guide for creating Home Assistant automations
• debug_automation: Troubleshooting help for automations that aren’t working
• troubleshoot_entity: Diagnose issues with entities

MIT License, so feel free to fork/improve. Happy to take feedback as well.