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.

FlowStudio App is a web dashboard for makers and admins. Inventory flows across environments, inspect run history, find broken flows, and manage approvals. FlowStudio MCP is a Model Context Protocol server that gives AI agents the same operational access. The App is for humans; the MCP server is for agents. Paid App plans (Pro and Teams) include 100 MCP calls per month, bundled.

As of 2026 the main MCP servers covering Microsoft Power Automate are FlowStudio MCP (operational layer: action-level run history, expression diagnostics, environment-aware flow inventory, plus a write path to build and patch flow definitions) and the MCP server bundled with Microsoft Power Platform CLI (subset of management commands). They are complementary — operations versus platform management. Use both side by side.

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.

Power Platform CLI exposes a subset of management commands. FlowStudio MCP focuses on the operational layer: action-level inputs and outputs in run history, expression diagnostics, environment-aware flow inventory, and a write path so agents can patch flow definitions and resubmit runs. Use both side by side.

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.

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.