Community integration: connect Microsoft Copilot Chat & Cowork to ha-mcp

[EBOOZ]

Hi team,

I've created a community project that enables Microsoft Copilot Chat and Copilot Cowork to use ha-mcp:
👉 https://github.com/EBOOZ/ha-mcp-plugin

The plugin acts as the Copilot-side integration for ha-mcp, allowing Copilot users to connect their Home Assistant environment through an existing ha-mcp endpoint.

I've also created a configurator to make generating the required Copilot plugin configuration easier.
👉 https://ebooz.github.io/ha-mcp-plugin/

I'd like to explore whether this could be included in the ha-mcp documentation as one of the available client integrations, alongside the other AI clients already documented by the project.

I'm happy to contribute:

• Copilot / Copilot Cowork setup documentation
• Configuration examples
• Screenshots
• Troubleshooting guidance
• Maintenance of the Copilot-specific instructions

If this is something you'd be interested in supporting as a community-maintained client integration, I'm happy to submit a PR or adapt the project/documentation to whatever structure fits ha-mcp best.

Feedback very welcome!

[Patch76]

@kingpanther13 @sergeykad If you have time, what do you think about it? I don't have any experience with Copilot or Copilot Cowork.

[kingpanther13]

Thanks for putting this together, @EBOOZ. I dug into Microsoft's docs, and I don't think a separate plugin is needed for either surface.

Copilot Cowork: a plugin package is how Cowork adds any custom MCP server, but the package itself is tiny: a manifest.json with an agentConnectors entry holding the ha-mcp URL and auth type, uploaded via Customize → Plugins → Add plugin. Cowork discovers tools live through tools/list and ignores mcpToolDescription even when it's present (docs). The bundled tool dump is only required at manifest 1.28. At 1.29, connector entries are URL-only, so there's no tool snapshot to ship or keep in sync with our releases. Cowork also supports OAuth and dynamic client registration, so ha_auth should work too, not just None on the secret webhook URL.

Copilot Chat: Copilot Studio has an MCP onboarding wizard (Tools → Add a tool → Model Context Protocol). You paste the server URL, pick None, API key or OAuth with dynamic discovery, and the tools are discovered automatically, with no package needed (docs). Declarative-agent MCP plugins also discover tools dynamically by default (docs).

So rather than linking a third-party generator, I think the better fit is adding Microsoft 365 Copilot Chat and Cowork setup instructions directly to our setup site: a minimal 1.29 Cowork manifest example, plus the Copilot Studio wizard steps. If you'd like to contribute that as a PR to the site, that would be welcome, since you clearly have the M365 environment to test it in.

[EBOOZ]

Thanks for digging into the docs, @kingpanther13! I missed the 1.29 manifest, which indeed discovers all tools available automatically.

Let me do some further testing to make sure it's as smooth as possible for end-users. I know a lot can be configured by administrators but in most environments these options are not available for end-users. Additionally, Copilot Studio is also something that is usually not available for regular users.

I plan to work on this on Saturday, and send you a write up with my findings.