Power Automate MCP server

power-automate-mcp-server

An MCP server that lets agents inspect, operate, and author Microsoft Power Automate cloud flows from a CLI/agent context — list and inspect flows, debug runs, check connections and owners, and (when explicitly enabled) enable/disable flows, cancel/resubmit runs, manage owners, and create/update/delete flows.

Primarily a management surface — the Power Automate portal's visual designer remains the better place to author complex flow logic — but createflow/updateflow/delete_flow are also available (write-gated) for programmatic authoring. Built on SomaMCP (telemetry, health/info/ dashboard, error classification) over FastMCP.

⚠️ Unofficial API. v1 targets api.flow.microsoft.com — the surface the Power Automate

portal itself uses. Microsoft labels it _"isn't supported. Customers should instead use the

Dataverse Web APIs." It is stable in practice and, unlike Dataverse, sees all** flows

(including personal "My Flows") and works on M365‑seeded entitlements (no Premium license).

Every tool's description carries this disclaimer. A supported Dataverse backend is stubbed

for the future (see src/backend/dataverse/README.md).

Quick start

pnpm install
cp .env.example .env          # set AZURE_CLIENT_ID (see "App registration" below)
pnpm build
pnpm dev:stdio                # local agent over stdio (device-code sign-in to stderr)

On first use the server prints a device-code prompt to stderr; open https://microsoft.com/devicelogin, enter the code, and sign in. The token is cached (TOKENCACHEPATH, mode 0600) and silently refreshed thereafter.

Add to an MCP client (stdio)

{
  "mcpServers": {
    "power-automate": {
      "command": "npx",
      "args": ["-y", "power-automate-mcp-server", "--stdio"],
      "env": { "AZURE_CLIENT_ID": "<your-app-registration-client-id>" },
    },
  },
}

Developing on this repo? It ships a project-scoped .mcp.json (stdio, local dist/bin.js). After pnpm build, export AZURECLIENTID and open the repo in Claude Code — the power-automate server loads automatically (complete the device-code sign-in once; the cached token is then reused).

App registration

This server ships no default client id — you register your own (one‑time):

single‑tenant if you'll only ever use one org).

1. Azure Portal → Microsoft Entra ID → App registrations → New registration.
2. Name it (e.g. power-automate-mcp). Supported account types: multitenant (or

http://localhost (unused by device code, but required to register the platform). Set "Allow public client flows" = Yes.

1. Authentication → Add a platform → Mobile and desktop applications. Add redirect URI

Automate / Microsoft Flow Service API. If it isn't in the picker, see "Token audience" below — this is the known friction point.

1. API permissions → Add a permission. You need a delegated permission for the Power

1. Copy the Application (client) ID → AZURECLIENTID.

Shortened. The full README is on GitHub.