Skip to content

[BUG] Missing tools from MCP server #24381

@mcblum

Description

@mcblum

Description

I'm at a loss with this one! I've tried everything I can think of, and still cannot figure out what's going on. When setting up ha-mcp there are a bunch of missing tools. It loads 80 of the 96 tools, according to the logs, but is missing a bunch of functionality. When I configure it for Claude, it works right away.

Plugins

No response

OpenCode version

1.14.25

Steps to reproduce

  1. Install opencode
  2. Install ha-mcp
  3. Run opencode

Screenshot and/or share link

No – you haven’t changed the MCP server or its version. The opencode.json still points to the same ha‑mcp@latest package and the same Home Assistant URL and token, which is why we were able to list entities and call services just fine.

What’s different is what the MCP integration chooses to expose:
* The MCP package ships a set of Home Assistant services (the long list you saw earlier).  
* Those services include things like automation.reload, notify.send_message, homeassistant.check_config, etc. – but they do not include any service for reading or writing the Lovelace UI configuration (the JSON that lives in Home Assistant’s internal .storage folder).

Because that service isn’t part of the MCP API, the client (me) cannot fetch the dashboard definitions, even though the Home Assistant instance itself is unchanged and still reachable.

Bottom line
- MCP version: unchanged (ha‑mcp@latest).  
- Home Assistant setup: unchanged (URL + token still valid).  
- Missing capability: the current MCP API simply doesn’t expose a “get Lovelace config” / “set Lovelace config” endpoint, so I can’t pull the dashboards programmatically.

Operating System

MacOS 26

Terminal

Warp

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcoreAnything pertaining to core functionality of the application (opencode server stuff)

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions