FlowStudio App
Inventory flows across environments, inspect runs, and catch failures before users do.
Inventory flows across environments, inspect runs, and catch failures before users do.
Let your agents inspect runs, build flows, trigger executions, and patch broken definitions.
One install in Claude Desktop, Claude Code, Copilot Studio, or Copilot Cowork.
Sign in with your Microsoft work account. Delegated permissions only.
Your agent reads run history, inspects actions, builds and patches flows on your behalf.
Need more? Contact us for Enterprise pricing with unlimited calls, SLA, and dedicated support.
Calls reset monthly on paid plans. Unused calls do not roll over.
Free Evaluation includes 100 calls total to use within 21 days.
Power Automate licensing still applies, including premium connectors and tenant policies.
“I had seen what John wanted to build, and cannot wait to see this come to life and grow with the Power Platform.”
Charles Lamanna CVP, Low Code Application Platform, Microsoft “❤ tags and organization features on FlowStudio App”
Brian Dang Power Apps Program Manager, Microsoft “In Microsoft we have TOO MANY Environments.. and I couldn't find a flow. FlowStudio took 2 seconds, scanned all my environments and found my flow!”
Jon Levesque Senior Power Platform Evangelist, Microsoft Used by Power Platform makers at
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, and Copilot Studio agents. 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.
Not directly. GitHub Copilot doesn't expose an MCP client for Power Automate, so it can't read run history or inspect action inputs and outputs. The same underlying models reached through Claude Code, Cursor, or another MCP-capable client — with FlowStudio MCP installed — can debug Power Automate flows. The capability lives in the MCP client, not the model.
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.
Full Q&A list on learn.flowstudio.app/faq.
Bring FlowStudio to your team, your flows, and your AI agents.