Would you use a MCP "plugin" addon for bulk extension of the HA voice assistant?

[hot crypt]

So I saw recently that next month we're enabling LLMs to use multiple MCP servers, but it occurred to me that if I wanted to easily add a bunch of features to HA assist but not create entities for them, MCP is kind of the ideal solution.

My idea and question is, if there was a single MCP server addon that had a configurable list of plugins (weather, traffic, local business hours, whatever else the community thinks of) that you could just install as an addon and drop various API keys into... would you use it? Or would it be preferable to have an MCP server per functionality?

For example, I want to ask about the weather in random places, but I don't need entities for every place. It's not something I'd use on dashboards but a very common freeform voice type question. It kind of fulfills a similar niche to Alexa Skills, and extending functionality is as simple as updating an addon config.

I was thinking if designed properly it could even support pluggable modules and if you want to extend it you just write the tool endpoints and drop a link to the git repo into your addon config and it will grab the plugin and let you use it, just like that, without having to worry about the MCP nuts and bolts or writing addon configs or managing 17 different MCP add-ons.

Thoughts?

[grand root]

I'd try that. weather, maps, time seems lame but yeah, time, memory... what else?

[hot crypt]

For me I was trying to hit the things that I tend to need myself most often from our Alexa that are otherwise annoying to implement in HA automations, which is usually the "one-off questions that I'll ask about a specific case once or twice and never again", so no specific entity would make sense to create. Other examples I've thought of:

• Upcoming concerts/events
• Read my last few messages from X contact?
• What's the homelab/device performing (Kube/docker-compose/ssh whatever)