mcp-power-automate

MCP.Pizza Chef: kaael1

Manage your Microsoft Power Automate cloud flows directly from your AI assistant by using this local server and browser extension. It captures your logged-in browser session to let you view, edit, validate, run, and revert flows safely without complex setup or admin permissions. You can also debug flow runs and add flows to unmanaged solutions. Setup involves adding the server to your MCP client and loading a Chromium extension, no API keys required.

Other

Use This MCP server To

Inspect and list my Power Automate cloud flows Edit and safely update a flow with AI assistance Validate and preview changes before saving a flow Run and test flows manually or by request trigger Review recent flow runs and diagnose failures Add existing flows to unmanaged Dataverse solutions Revert the last update if a change causes issues

README

MCP Power Automate cover: inspect, validate, edit, and revert Power Automate flows with an MCP agent

MCP Power Automate

Local-first MCP server and Chromium extension for AI-assisted Microsoft Power Automate work.

Use your existing logged-in browser session to let an MCP client inspect, validate, edit, run, review, and revert Power Automate cloud flows. No Microsoft Entra ID app registration, admin consent flow, or custom enterprise application setup is required to get started.

Early public signal: 15,000+ LinkedIn post views and 14 GitHub stars while the project is still small, practical, and moving fast.

Why It Exists

Power Automate is powerful, but AI agents need more than raw convenience before they should touch real flows. This project keeps the workflow visible and reversible:

  • The browser extension captures the active Power Automate context and compatible tokens from your own Chromium session.
  • The MCP server exposes a v1 command surface for targeting, reading, previewing, validating, saving, run inspection, and rollback.
  • The extension stays mostly passive: status, diagnostics, and review surfaces instead of mystery buttons that hide what changed.
  • Local state, snapshots, and backups stay on your machine.

What It Can Do

Area Capabilities
Context Detect browser-captured flows, list flows, and explicitly lock onto a target flow.
Safe editing Read the flow, preview the smallest candidate update, validate, save, review the diff, and revert.
Debugging Inspect recent runs, latest run details, and action-level failures.
Testing Invoke safe manual/request trigger flows and wait for the resulting run.
Solutions List unmanaged Dataverse solutions, inspect solution components and environment variables, add existing flows, and create blank flows inside solutions.

Write operations are deliberately scoped. The MCP does not expose solution deletion, component deletion, managed-solution modification, environment-variable writes, or blind production edits as the default path.

Quickstart

Register the MCP in Codex:

codex mcp add power-automate-local -- npx -y @kaael1/mcp-power-automate

Find the packaged extension path:

npx -y @kaael1/mcp-power-automate extension-path

Load that folder in Chromium:

  1. Open chrome://extensions or edge://extensions.
  2. Enable Developer Mode.
  3. Choose Load unpacked.
  4. Select the folder printed by extension-path.

Then open or focus a Power Automate flow page. The extension captures the session and target context automatically.

Check readiness:

npx -y @kaael1/mcp-power-automate doctor

mcp-power-automate FAQ

Can I use this to safely edit and manage my Microsoft Power Automate flows?
Yes — it lets you inspect, validate, edit, run, and revert Power Automate flows using your existing browser session without complex setup.
Can I debug and test Power Automate flows with this?
Yes — you can inspect recent runs, check failures, and manually trigger flows for testing.
Does this require a Microsoft Entra app registration or admin permissions?
No — it works with your logged-in browser session and needs no extra app registrations or admin consent.
Which apps or clients support this MCP server?
It works with MCP clients that can connect locally; setup involves adding it to Codex and loading a Chromium extension.
Do I need an API key or special account to use this?
No special API key is needed; it uses tokens from your logged-in browser session.
How hard is it to set up?
Setup is moderate — you paste a small config snippet and load a browser extension in Chromium.
Can I use this to delete flows or modify production environments directly?
No — write operations are limited to safe edits and adding flows to unmanaged solutions only.