Tools listed in the DISABLED_TOOLS or PINNED_TOOLS env vars are locked read-only

[cciprian5]

I have been looking around, but I do not find where these environment variables would be defined

Running Home Assistant OS 2026.7.1 on Raspberry Pi 4

[kingpanther13]

Can you be more specific? What installation mode of HA-MCP are you using and where are you seeing this? The easiest way to control these is via the web ui which every install method has at this point, you can ask your LLM to use the get overview tool and it should tell you how to connect to the web UI no matter what version you have. The custom component is the easiest one to deal with, it automatically will put a thing in your sidebar to get to the settings UI.

[cciprian5]

I have tried with custom component and I was unable to get a connection from MCP to HA (various errors on https/ssl).
Now I have installed the addon, but still can't unlock files and search&discovery tools

This is in the addon page

And this in the configuration of the addon

[kingpanther13]

Are you using the web UI within the addon, or is this the same web UI from custom integration? The addon doesn't make the sidebar link the way custom component does, you have to access it from the addon page. Also what you're showing me is just some warnings and the configuration settings can you show me what you mean by you can't unlock files and the search tools? File tools are gated behind beta flag in the advanced server settings in Web UI, but search tools should be accessible at all times.

[cciprian5]

Yes, I am using the web UI in the addon, not the one from the custom integration.

This is what I have for the search tools

[kingpanther13]

Your tools are active. This is a graphical bug I'll be fixing soon, good catch on it.

[cciprian5]

Enabling the beta, I have this error message. Isn't the addon independent of the custom component?

Could not reach the ha_mcp_tools component: { "success": false, "error": { "code": "COMPONENT_NOT_INSTALLED", "message": "The installed ha_mcp_tools custom component is too old: the get_caller_token bootstrap service is not registered (pre-0.5.0). This ha-mcp release requires >= 0.11.0. Update via HACS and restart Home Assistant.", "suggestion": "HACS \u2192 Integrations \u2192 HA MCP Tools \u2192 Update", "suggestions": [ "HACS \u2192 Integrations \u2192 HA MCP Tools \u2192 Update", "Restart Home Assistant after update completes", "Then retry the operation" ] } }

[kingpanther13]

Yes addon is independent of custom component server, but the tools custom component is and always has been required to use the filesystem and beta tools, it is required even with the current custom component server.

That looks like a graphical bug, I think I have the same bug, check your AI tool list, the search tools should be present. It shouldn't be possible to disable them.