Repository navigation
Diagnosed the catalog issue: the installed Power Automate plugin's . #5514
Description
Diagnosed the catalog issue: the installed Power Automate plugin's .mcp.json already registers FlowAgent, and its bundled server starts successfully. I launched the installed server locally and queried its MCP tools/list response; it advertises 62 tools, including create_flow, preflight_flow, and validate_flow. Therefore, the server code/config is present—the missing tools are a stale or unsynchronized Copilot session catalog. Recommended fully quitting and reopening Copilot into a fresh session, then updating/reinstalling the power-automate plugin if needed; if still absent, report the verified discrepancy to Copilot/plugin support.
| Field | Value |
|---|---|
| App version | 1.1.35 |
| OS | Windows 11 (10.0.26300) |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 1 |
Activity
cwebster-99 commentedon Nov 6, 2026
Thanks for narrowing this down to a discrepancy between the installed server's tools/list response and the tools available in the app session. To reproduce that discrepancy, please share the Power Automate plugin version and installation source, the steps that make its tools disappear from the app, the selected model, and whether the affected session is local or remote. Does the problem still occur in a fresh session after fully quitting and reopening the desktop app?
If there is a plugin-discovery or tool-catalog error, a small redacted excerpt would help. Please exclude tokens, credentials, session transcripts, and unrelated logs. The successful standalone server response is useful evidence, but does not yet establish why the app catalog differs.
chuwik commentedon Nov 6, 2026
Thanks for the detailed report, and for confirming the server itself starts and lists its tools.
We found and fixed one case that produces this: if a plugin is installed from outside the app, for example with a terminal command or by the agent during a chat, its tools didn't appear in a chat that was already open until the app was restarted or a new chat was started. The fix will ship in an upcoming release.
To confirm it's the same case for you, could you tell us: