What it does

Drives Power Automate from a terminal-based AI coding agent. You install a plugin into GitHub Copilot CLI or Claude Code, describe what you want in plain language, and the agent creates, edits, runs, debugs and manages cloud flows through a bundled MCP server. It also lists and runs desktop flows, though it can't edit desktop scripts.

Key facts

• Ships from the Power Platform Skills marketplace (microsoft/power-platform-skills), installed as a plugin — not an npm package and not a remote MCP host you configure yourself. The MCP server comes bundled.
• Prerequisites are real: Node.js 18+, the Azure CLI signed in with the same work account (az login --allow-no-subscriptions), and a Power Automate licence covering the flows and connectors in play. GitHub CLI only matters if you want /report-issue.
• Everything runs as your signed-in identity. Permissions, licensing, connector policies, DLP and tenant restrictions all apply exactly as they would in the maker portal. There is no service principal and no elevation.
• Ten skills, invokable as slash commands or conversationally: /setup, /browse-flows, /create-flow, /build-flow, /debug-flow, /diagnose-flow, /manage-flows, /manage-desktop-flows, /route-environments, /report-issue.
• New flows are created in a stopped state so you review before enabling. Edits to existing flows can preview the change and take a restorable backup first.
• /diagnose-flow is the deeper of the two debug paths — it wants environment, flow and run IDs and goes after root cause; /debug-flow works from a vaguer starting point.
• Bundles the Microsoft Learn MCP server alongside, so the agent can cite current Learn guidance rather than working from whatever it was trained on. Learn is read-only reference; the actual Power Automate operations go through the plugin's own server.
• Desktop flow support is discovery, execution and machine groups only. No script editing.
• /report-issue files a public GitHub issue. Tenant IDs, environment IDs, internal URLs and customer data all have to come out first.
• Part of a pattern, not a one-off: equivalent plugins exist for Power Pages and for canvas apps in Power Apps.

When to use / skip

Use it where the person building flows already lives in a terminal — a developer doing ALM work, someone maintaining a large estate, anyone doing bulk operations like inventory reports, health checks across connections, or copying flows between environments. The batch and diagnostic skills are the real value; they're the jobs that are tedious in the maker portal and quick here.

Skip it for citizen makers. The prerequisites alone (Node, Azure CLI, a coding agent subscription) put it outside the audience Power Automate is usually sold to, and a business user who can't read a flow definition can't review what the agent proposes — which is the one thing this tool requires you to do properly.

Also skip it as a production change mechanism until you've decided how it fits your ALM story. It edits live flows.

Configuration decisions

• Who gets it, and whether that population overlaps with people who hold broad flow permissions. The plugin inherits their access wholesale.
• Whether it's allowed to touch production environments at all, or confined to dev and test with promotion through solutions as normal.
• Which coding agent — GitHub Copilot CLI or Claude Code — and whether that licence already exists or is a new line item.
• Whether automatic marketplace updates stay on. They keep you current on fixes but mean the skill set can change under you between engagements.
• How this reconciles with your source-control and change-management process, given that agent-made edits land directly on the flow rather than through a solution export.

Gotchas

• It writes to live flows. Backups and previews exist, but the default mental model people bring from Copilot in the designer — that it drafts and you save — doesn't hold here. /manage-flows will publish.
• The Azure CLI session is a separate sign-in from your Power Platform one, and some connection operations still bounce you to a browser for interactive consent. A /setup that passes doesn't guarantee every connection task runs unattended.
• It inherits the user's permissions, which is the security story and also the risk. Give it to someone with System Administrator on the environment and the agent has System Administrator. Nothing in the plugin scopes that down.
• AI-generated flow definitions are explicitly flagged by Microsoft as possibly inaccurate. Complex expressions, connection references and managed-solution components are where that bites.
• Issue reports are public by default. That's a data-leakage path sitting behind a slash command, in a tool aimed at people working with production tenants.
• The skill set changes as the marketplace updates, so documentation and internal runbooks written against today's commands will drift.

Consultant notes

• Treat this as a developer tool that happens to point at Power Automate, and govern it that way. The clients who'll get value are the ones with a platform team already doing ALM properly; handing it to a citizen-maker community is how you get undocumented production edits nobody can trace.
• The permission inheritance is the conversation to have with the client's security function early. They'll ask "what can it do?" and the honest answer is "everything the person running it can do, faster" — which is fine, but it needs saying out loud rather than discovered during a review.
• Where it genuinely earns its place is estate management: connection health across hundreds of flows, inventory reports, finding what broke overnight. Scope it into support and operations, not into build. That framing also gets it past change control more easily.
• Watch the ALM seam. An agent editing a flow directly bypasses the solution-and-pipeline route most mature tenants have spent effort establishing, and the two habits will fight. Decide which environments it's allowed in before anyone installs it, not after.
• The public issue reporting needs a line in whatever acceptable-use note you give the client. It's a small thing that becomes a large thing exactly once.

---

Worth revisiting as the Power Platform Skills marketplace fills out — the equivalent Power Pages and Power Apps plugins suggest this is a direction rather than a single release, and the skill list is likely to move.