FlowStudio — Power Automate operations, a Model Context Protocol server, and an AI agent that fixes flows

A Model Context Protocol server that gives AI agents action-level access to your Power Automate cloud flows. Agents can read run history, inspect action inputs and outputs, build and modify flow definitions, and trigger or resubmit runs, all using your delegated Microsoft permissions.

It depends on who you want doing the work. FlowStudio App is a web dashboard you drive yourself: inventory flows across environments, inspect run history, find broken flows, and manage approvals. FlowStudio MCP gives an AI agent you already use — Claude, Codex, Copilot — that same operational access. FlowStudio AI is for when you have no agent of your own: a chat window with the agent included, running on FlowStudio MCP underneath. Paid App plans (Pro and Teams) include 100 MCP calls per month, bundled.

A chat window on the web that operates your Power Automate flows for you. Ask why a flow failed and it reads the run history and finds the cause; describe an automation in plain English and it builds the flow. Unlike FlowStudio MCP, you do not need an AI agent of your own — this one comes with it. It uses your delegated Microsoft permissions and never changes a flow without your go-ahead. $39 per month, with a 14-day free trial. A Microsoft Teams version is coming soon.

Three, and they are not the same thing. FlowStudio MCP is a hosted server for any Model Context Protocol agent, covering action-level run history, expression diagnostics, a tenant-wide flow and maker inventory, and a write path to build and patch flows. Microsoft's Flow Agent is Microsoft's own Power Automate server, free, and runs locally alongside an AI agent on your own machine. The Power Platform command-line tool also ships an MCP server, but that one is scoped to app and solution lifecycle in local development. Running more than one side by side in the same session is fine.

Yes. FlowStudio MCP works with Claude (Desktop and Claude Code), OpenAI Codex, M365 Copilot, Copilot Cowork, Copilot Studio, and GitHub Copilot (VS Code agent mode). Any MCP-compatible client that supports the OAuth handshake or an x-api-key header can connect.

The difference is where it runs. Microsoft's Flow Agent needs an AI agent running locally on your machine — it is free and good at building and debugging a flow while you work, but the work only happens in a session you are sitting in front of, and stops when that machine does. FlowStudio MCP is a hosted server, so it has an address other software can call: cloud agents, scheduled monitors, a chat assistant, or your own systems reach it with nobody at a keyboard. That is also what makes the rest possible — a cached, tenant-wide store of every flow, maker and Power App behind governance and monitoring across environments, and a separately revocable key per client. On single-flow work the two genuinely overlap, and plenty of teams will want both: author locally, monitor and integrate centrally. Full side-by-side comparison on learn.flowstudio.app.

Yes. The Web API only returns top-level run status. FlowStudio MCP exposes action-level inputs, outputs, loop iterations, and nested child-flow failures, so an AI agent can find the actual root cause without you opening the portal.

Yes, in VS Code. GitHub Copilot's agent mode supports MCP servers, so with FlowStudio MCP installed it can read run history, inspect action inputs and outputs, and build, patch, and trigger flows. The capability lives in the MCP client, not the model — Copilot surfaces without an MCP client can't.

Through your delegated Microsoft permissions. You sign in with your Microsoft work account, and FlowStudio operates Power Automate with the same access you have. No service principals, no stored secrets, no mailbox or SharePoint file scopes. See the security page for details.

You can still connect. Install the FlowStudio browser extension, and your agent reaches Power Automate through the session you are already signed in to — so there is nothing for an administrator to approve, and your Power Automate token never leaves the browser. Set it up from the FlowStudio MCP dashboard. Two things to know: the one-time setup needs a desktop browser (Chrome or Edge), and calls run while that browser is open and signed in.

Yes. With FlowStudio MCP you describe the automation in plain English and an AI agent — Claude, OpenAI Codex, GitHub Copilot, or M365 Copilot — builds the Workflow Definition Language JSON and deploys the live flow using your delegated Microsoft permissions. No portal, no hand-written JSON.

Free, open-source Power Automate MCP servers exist and are a fine way to start — they typically run locally or off a browser session and focus on creating and managing flows. FlowStudio MCP is a hosted server that operates through your delegated Microsoft permissions, with action-level run-history debugging — inputs, outputs, loop iterations, and nested child-flow failures — and a write path to patch live flow definitions and resubmit runs.

Yes. A tenant admin adds FlowStudio MCP once from the Microsoft Marketplace, and everyone uses it inside Copilot Cowork, or their own agent, by asking in plain English. Calls are pooled across the tenant. Tenant Starter is free and auto-provisioned when you add the Copilot Cowork plugin; Team (5,000 calls/month) and Business (15,000 calls/month) are pooled plans billed and managed by Microsoft. Per-seat individual plans are also available.