Labsco
MCP SERVER

Flow Studio - Power Automate MCP Server

by ninihen1 ↗

See what the Power Automate portal shows you — action inputs, outputs, loop iterations and child-flow failures — from an agent.

Workflow Automation & iPaaS
Summary
Your agent stops being blind at the point the flow broke.

A failed run in the portal is a click-through exercise; through here it is a query. The agent reads the failing action's actual inputs, follows the call into the child flow, and can push the corrected definition back — without you acting as the middle-man between it and the browser.

What it is

A hosted MCP endpoint plus five agent skills for Power Automate. The gap it fills is specific: the Graph API returns top-level run status, so an agent can see that a flow failed but not why. This exposes the action-level detail a human gets in the portal — inputs, outputs, error detail, child-flow runs and per-iteration loop data.

What you get
  • Live operation — list flows, read definitions as full JSON, check runs, resubmit and cancel, and deploy a fixed definition with `update_live_flow`
  • Action-level visibility — the inputs and outputs of every action, error detail beyond the status code, child flow run details, and loop iteration data the agent can scan all at once
  • Five skills, each following the Agent Skills specification: `power-automate-mcp` for connecting and operating, `power-automate-debug` for a step-by-step diagnostic process, `power-automate-build` for scaffolding and deploying definitions, `power-automate-monitoring` for flow health, failure rates, maker and Power Apps inventory, and `power-automate-governance` for impact classification, orphan detection, connector audits and archive scores
  • Worked investigations in the repository, including an expression failure traced from parent flow through a child flow into a loop iteration
Requirements

A FlowStudio subscription and an API key, passed as the `x-api-key` header against the endpoint `https://mcp.flowstudio.app/mcp` over HTTP transport — there is nothing to install for the server itself. The monitoring and governance skills read a cached daily snapshot rather than live data and need FlowStudio for Teams or MCP Pro+; the first three skills use live API calls. Skills install through the Claude plugin marketplace, `$skill-installer` in Codex, `npx skills add`, ClawHub or Smithery, or by copying the folder into wherever your agent discovers skills.

Setup effort

One command plus a key — claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp --header "x-api-key: <YOUR_TOKEN>", then supply credentials