[BUG] v7.5.0: only newly-added tools register in stdio mode; ~80 pre-existing tools missing

[schford]

Summary

After uvx ha-mcp@latest upgraded from v7.4.x to v7.5.0 (released 2026-05-13 12:04 UTC), Claude Desktop only sees 6 tools from a server that previously exposed the full ~85-tool surface.

Tools observed (post-upgrade)

• ha_call_event
• ha_config_get_scene
• ha_config_set_scene
• ha_config_remove_scene
• ha_set_area_or_floor
• ha_remove_area_or_floor

Tools missing (full categories)

Dashboards, Service & Device Control (ha_get_state, ha_call_service, …), Search & Discovery (ha_search_entities, ha_deep_search, ha_get_overview), Utilities (ha_eval_template), System (ha_check_config, ha_get_logs, …), Automations, Scripts, Entity/Device Registry, History, Helpers, Files, HACS, Groups, Labels, Zones, Todo, Calendar, Camera, Blueprints, Add-ons, Integrations, Energy.

Pattern

5 of the 6 surviving tools are exactly the surface added in v7.5.0 (ha_call_event, scene config tools). The 6th pair is the renamed area/floor tools. Consistent with registration aborting mid-load after the new tools succeed, before older modules register.

Environment

• Transport: stdio via Claude Desktop on Windows 11 (MSIX install)
• Launch: uvx ha-mcp@latest
• Two separate HA targets (MB, CM), both affected identically
• Env vars set: HOMEASSISTANT_URL, HOMEASSISTANT_TOKEN, `EN

[github-actions[bot]]

⚠️ Triage bot temporarily unavailable.

The automated triage hit an internal error. Your issue will be triaged manually — no action needed on your part.

🤖 Automated triage by Issue Bot

[kingpanther13]

Try refreshing your tool list, or disconnecting and reconnecting the mcp server in Claude. It can get weird sometimes on updates. If it still isn't working after that let me know and I'll dig deeper.

@Patch76 are you by chance able to investigate this please? If you're able, please Try installing stable version via stdio and see if you can replicate the bug.

[schford]

Restarted claude and also tried full reboot no joy. Reverted to previous version and works a ok.

[Patch76]

@kingpanther13 Can't ... off for a short vacation, sorry.

[kingpanther13]

@Patch76 no worries.

@schford I Just did a fresh install using the install guide by running irm https://raw.githubusercontent.com/homeassistant-ai/ha-mcp/master/scripts/install-windows.ps1 | iex and then editing the config file and providing the LLAT, and it is set to ha-mcp@latest . It connects just fine and is able to see most tools, though I discovered that it cannot see the skills tools; I'm opening another issue regarding that. I'm wondering if maybe the issue you're experiencing is due to Claude's built in deferred tools or something. Try to change back to @ latest, restart Claude Desktop. Go to the "customize" section on the left, then select your MCP server (named Home Assistant by default). You should see a list of all of the tools come up on the right side of the screen. If you're only seeing the 8 tools there then this is a deeper issue, but if you see roughly 80 tools then everything should be working fine, it could just be Claude getting confused with using its built in toolsearch.

[kingpanther13]

Since we haven't gotten a response in a few days, I'm going to convert this to a discussion, if you need more help please open a new issue but this is either a transient issue on your end or an agent behavior issue from what I can tell.

[schford]

Sorry for the delay in coming back to you. I was away in Las Vegas for my birthday and didn't have a laptop or anything with me, just the phone. I'm testing it now. I'll come back to you.

[schford]

Thanks, you were absolutely correct. For some reason, most of the tools had been set to blocked. And on version 7.4.0, that didn't seem to affect the ability for them to be used, whereas on the latest release it did. How strange.

[kingpanther13]

No worries! We appreciate the contribution either way, I'm glad you got it working!