Would you use a generic MCP "plugin" add-on for extending HA assist functionality?

So I saw recently that next month we’re enabling LLMs to use multiple MCP servers/control systems (vs right now they only support 1 apiece), but it occurred to me that if I wanted to easily add a bunch of features to HA assist but not create entities and separate integrations for them, MCP is kind of the ideal solution for low-touch integrations.

My idea and question is, if there was a single MCP server addon that had a configurable list of plugins for different tools (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 a separate MCP server per functionality?

For example, I want to ask about the weather in random locations, 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 could be as simple as updating an addon config.

I was thinking if designed properly it could even support pluggable modules so 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?

I’ve already built the first part (a weather MCP server with SSE support and override configs) but am curious to hear other thoughts before investing time to modularize it, vs turn it into a template for churning out more HA compatible MCP servers. I’d be particularly curious to hear @allenporter 's thoughts since he’s implementing the LLM extension to support multiple MCP servers/LLM APIs in addition to HA Assist on 1 voice assistant.

I can see an add on being useful for a couple key MCP servers. One for example is this fetch server (or `puppet)-- which you can then call from a script to do other useful things Home Assistant Model Context Protocol.md · GitHub

So i think of it like: Add MCP servers, add scripts to turn them into entities or use them in automations if you like. Blueprints may be a light weight way to share recipes.

“configurable list of plugins for different tools” sounds like the most flexible solution and fastest. I would prefer this way.