MCP Power Automate

Local MCP server, Chromium extension, and optional Codex skill for operating Microsoft Power Automate flows from a local browser-backed session.

No Microsoft Entra ID app registration, admin consent, or custom enterprise app setup is required. This MCP uses your existing logged-in browser session instead, which is often much easier to adopt inside locked-down companies.

Built for MCP users who want to do real Power Automate work without getting stuck in enterprise auth setup, tab confusion, or blind edits.

This project lets an agent:

• list flows from the current environment, including owned and shared-visible flows
• select an explicit target flow instead of following the active tab
• read, validate, update, create, clone, test, inspect runs, and revert flows
• use the browser only for auth and visual context while the MCP owns the workflow logic

The server is MCP-client agnostic.

• Use the MCP from Codex, Claude clients, Gemini clients, OpenCode, or any other MCP client that supports local stdio servers.
• The bundled power-automate-mcp skill in this repository is Codex-specific helper guidance, not a requirement for the MCP itself.

Why MCP users install this

• No Microsoft Entra ID app registration just to get started
• Explicit target flow locking instead of following whatever tab happens to be active
• Browser-backed auth that matches how teams already work in Power Automate
• Structured review diff plus one-step rollback after saves
• Local-first architecture that keeps the browser for context while the MCP handles the workflow logic

Why this is useful

| Common pain | What this repo gives you | | --- | --- | | Enterprise setup friction before first success | Browser-backed auth from your existing logged-in session | | Risk of editing the wrong flow | Explicit set_active_flow targeting plus current-tab sync | | Hard to trust AI changes | Post-save review diff and one-step revert | | Slow manual inspection and run triage | MCP tools for flow reads, validation, runs, actions, and trigger tests |

Install in 60 seconds

Install the optional Codex skill from GitHub:

npx skills add kaael1/mcp-power-automate --skill power-automate-mcp

Register the MCP locally:

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

Load the extension:

1. Open chrome://extensions or edge://extensions
2. Enable Developer Mode
3. If you are working from a clone, run bun install and bun run build
4. Click Load unpacked
5. Select the dist/extension folder

Open Power Automate, refresh any flow page, and ask your MCP client to:

1. list_flows
2. set_active_flow
3. get_flow

In practice, most users start with three wins:

1. inspect a real flow without hand-copying JSON
2. make a focused change and validate it
3. review or revert the last save with confidence

If this saves you time, star

... View full README on GitHub