FlowStudio MCP vs Microsoft's Canvas Authoring MCP server
Last updated 25 October 2026. FlowStudio’s canvas tools are a Preview, included in every account and free until 30 November 2026.
Two MCP servers now let an AI agent change a Power Apps canvas app. Microsoft’s runs on your machine inside an open Studio session and validates what it writes. FlowStudio’s runs as a hosted service, works from the agent you already use, and lands every change as a draft. This page is about which one fits your situation.
| The short version: working in a coding agent with Studio open and the YAML validated as it is written, Microsoft’s. Creating or changing an app from ChatGPT, Claude, Copilot Studio or Cowork, with a draft between the agent and your users, and the same agent fixing the flows behind it, FlowStudio. Both can sit in one coding agent. |
What each one is
In late August 2026 Microsoft published Create and edit canvas apps with AI code generation tools, a guide to its Canvas Authoring MCP server. It installs as the canvas apps plugin from the microsoft/power-platform-skills repository for GitHub Copilot CLI, Claude Code and VS Code. You open the app in Power Apps Studio with coauthoring on, connect the tool to that session, describe what you want, and it generates .pa.yaml, validates it, and syncs it into Studio.
FlowStudio MCP is a hosted MCP server for Power Automate. It carries fourteen canvas app tools, in Preview since September 2026: create an app or open one you have, read its screens, controls, Power Fx and data sources, edit them in a session, add a SharePoint, SQL, Excel or Dataverse table, push a draft, diff versions, publish. The agent can be ChatGPT, Claude, Copilot Studio, Cowork, Codex, GitHub Copilot or any MCP-compatible agent, and it is the same connection the agent uses for flows. The walkthrough is on Edit Power Apps canvas apps with your AI agent.
Both are real, both work. We have used both.
Side by side
Microsoft’s details checked against its Microsoft Learn guide, dated 27 August 2026 and last updated 13 October 2026, on 24 October 2026. Microsoft ships fast. Check theirs before you decide.
| Dimension | Microsoft Canvas Authoring MCP server | FlowStudio MCP canvas tools |
|---|---|---|
| What it is | A free plugin plus a local MCP server, driven by a coding agent on your machine | Fourteen tools on a hosted server your agent already talks to for flows |
| Where it runs | Your machine. Needs the .NET 10 SDK | Hosted. One address and a sign-in or key |
| Agents | GitHub Copilot CLI, Claude Code, VS Code, and other coding agents with plugin support | ChatGPT, Claude, Copilot Studio, Cowork, Codex, GitHub Copilot, and any MCP-compatible agent |
| Starting point | A blank app you created and saved, or an existing app | A phone, tablet or responsive blank, a split-screen or sidebar layout, a copy of an existing app, or an existing app |
| Studio | Open, with coauthoring on, and the tab kept open for the whole session | Closed while the agent works. Reopen it to look at the draft |
| How changes land | Generated .pa.yaml is synced into the live coauthoring session; you publish from Studio |
Edits go to a server-side session, a push lands a draft version, publish is a separate call |
| Checking formulas | Validates the generated YAML against its server and fixes validation errors before syncing | A Power Fx check that warns before a push and does not block it |
| Versions and conflicts | Studio’s own version history and coauthoring | Every draft is a version. Two versions diff per control and property. A push is refused if the app moved since the session started |
| Data sources | Discovered through the coauthoring session; add new ones through the Studio Data panel | Read from the app package with columns and types, Dataverse included. The agent can add a SharePoint, SQL, Excel or Dataverse table, and re-read a Dataverse table for new columns |
| Flows and the app together | Canvas apps only. Microsoft’s flow tooling is a separate plugin, FlowAgent | The same server reads, debugs, builds and edits the flows the app calls |
| Cost | Free. You bring a Power Apps licence and the .NET 10 SDK | Free while in preview, which ends 30 November 2026. From 1 December each canvas call counts as one MCP call. Starter is free, 100 calls over 21 days |
| Status | Guide on Microsoft Learn dated 27 August 2026, updated 13 October, with no preview label. Microsoft says the tools make a best-effort attempt and you are responsible for validating the result | Preview, included in every account |
The main difference: Microsoft’s edits inside an open Studio session and validates first. FlowStudio’s pushes a draft from a hosted server and lets you check it before anyone sees it.
What is the difference in practice
A session in Studio, or a draft on a server
Microsoft’s tool is a co-author. It works inside the Studio session you have open, its changes appear there, and you publish from Studio as you always have. That is a good fit for a developer building a screen with a coding agent beside them.
FlowStudio’s tool works on its own copy of the app. It downloads the app, edits a session on the server, and pushes a draft. Your users are on the published version the whole time, and the push is refused if a maker changed the app while the session was open. That is a good fit for an agent that runs without you watching, and for the person whose agent lives in ChatGPT or Cowork rather than a terminal.
Validation before, or a warning before and a draft after
Microsoft validates the YAML it generated and fixes errors before the sync. FlowStudio’s formula check runs Microsoft’s open-source Power Fx checker and warns, and the draft is where you see the result before anyone else does. If you want the tool to refuse bad formulas outright, Microsoft’s does more of that today.
The app and the flows behind it
Most canvas apps call flows. With FlowStudio the agent that reads the failed run and patches the flow is the same agent, on the same connection, that opens the app that calls it. With Microsoft’s tooling those are two plugins.
When to pick which
Pick Microsoft’s Canvas Authoring MCP server if...
- You want the agent to generate whole screens as YAML and have them validated as it goes
- You work in GitHub Copilot CLI, Claude Code or VS Code and keep Studio open beside it
- You want the generated YAML validated and corrected before it reaches the app
- You want a free tool and have the .NET SDK on your machine
Pick FlowStudio MCP if...
- The agent you use is ChatGPT, Claude, Copilot Studio or Cowork, or it runs in the cloud without a laptop
- You want changes, to a new app or one that exists, to land as a draft you check before users see them
- Someone else may be editing the app, and you want a push refused rather than merged silently
- The same agent should fix the flows the app calls
If two of those are you, the fastest way to check is to run it on a test app.
Start your free evaluation Starter plan: 100 calls, 21 days, no credit card
Use both if...
- Your developers build new screens with Microsoft’s tool in Studio, and the rest of the team changes existing apps and the flows behind them through FlowStudio from wherever they work. Keep the two on different apps at the same time: a Studio save writes Studio’s copy over the head, and a FlowStudio push refuses when the head moved.
Questions
Is Microsoft’s Canvas Authoring MCP server free?
Yes. The canvas apps plugin is on GitHub in the microsoft/power-platform-skills repository and the server ships as the NuGet package Microsoft.PowerApps.CanvasAuthoring.McpServer. You bring your own machine, the .NET 10 SDK, and a Power Apps Studio session.
Can I run both?
Yes, they register side by side in the same coding agent. Keep them on different apps at the same time. Microsoft’s tool works inside an open Studio session, and a Studio save writes Studio’s copy of the app over whatever FlowStudio pushed, so use one path per app per session.
Does FlowStudio need Power Apps Studio open?
No. The FlowStudio server downloads the app package itself, edits a copy in a session, and pushes a draft. Close Studio while an agent session is open, and reopen it afterwards to look at the draft.
Which one checks Power Fx formulas?
Both, differently. Microsoft’s validates the generated YAML against its server and fixes validation errors before it syncs. FlowStudio’s check_canvas_formula runs Microsoft’s open-source Power Fx checker and warns before a push; it is in Preview and does not block the push.
Can FlowStudio create a new canvas app?
Yes. It starts an app from a phone, tablet or responsive blank, a split-screen or sidebar layout, or as a copy of an existing app, then edits it like any other. Microsoft’s tool starts from a blank app you created and saved in Studio, with coauthoring turned on.
Does either work from ChatGPT or Claude in the browser?
FlowStudio does. It is a hosted server, so ChatGPT, Claude, Copilot Studio and Cowork connect to it the same way a coding agent does. Microsoft’s runs as a local plugin for GitHub Copilot CLI, Claude Code and VS Code.
Start here
Free evaluation: 100 calls, 21 days, no credit card. Connect your agent and ask it to open a test app.
Start your free FlowStudio MCP evaluation
The walkthrough: Edit Power Apps canvas apps with your AI agent · Tools reference · Add FlowStudio to ChatGPT or Claude · The flow side: FlowStudio MCP vs Microsoft FlowAgent · FlowStudio MCP vs the Power Platform CLI MCP
FlowStudio is an independent product and is not affiliated with, endorsed by, or sponsored by Microsoft Corporation. Microsoft, Power Automate, Power Apps, Power Platform, and Copilot are trademarks of the Microsoft group of companies.