r/homeassistant 16h ago

Support MCP Issues

I spent 4-6 hours working on getting the home assistant MCP server running. I was able to confirm that with the home assistant API key it would return server generic info with empty tools. Then as a test I would give it the wrong api key and it would auth error.

I noticed the project hasn't had new commits in 2 months which is a long time for a MCP server. Has this project been abandoned? Anyone had success getting it to expose tools or anything useful? I don't see any additional configuration needed on the actual MCP server itself. It appears to just be installed on home assistant.

I was actually gonna build my own MCP server but after playing around with the home assistant API I realized it's gonna be too much work to maintain. Maybe the developers realized MCP isn't of much value here and there is a better approach?

5 Upvotes

2 comments sorted by

2

u/LightBrightLeftRight 15h ago

I had some trouble initially, but it's working for me in LM Studio now. Here's what I have for my mcp.json:

{
  "mcpServers": {
    "Home Assistant": {
      "command": "mcp-proxy",
      "env": {
        "SSE_URL": "https://***homeassistant.my.domain***/mcp_server/sse",
        "API_ACCESS_TOKEN": "***long-term-token***"
      }
    }
  }
}

I also needed to install mcp-proxy in my global environment so it could be run from LM Studio without special commands. This is on a mac btw.

That said, the HA MCP server still needs a lot of work. Definitely more of a stub than a completed project.

First on my wishlist is a better data-getter than getContext(). I really want to write automations/scripts/cards with the LLM just going in and getting the right entities, clarifying with me as it goes. If they put in addAutomation(), addScript(), well that's gravy for me.

1

u/third_najarian 5h ago

I really wouldn’t read much into the 2 months. I’m building an MCP server right now for a different project. Honestly, once the tools are in place I don’t foresee huge changes until models change.