MCP Power Automate MCP Server

Connect MCP Power Automate to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Local MCP for Power Automate flows with browser-backed auth, extension, and Codex skill. The mcp power automate mcp server is what makes that connection.

What the server does

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

• 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

Installation

@kaael1/mcp-power-automate on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Where it fits

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by kaael1; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.