Skip to content

FlowStudio MCP vs Microsoft's Canvas Authoring MCP server

Last updated 7 November 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 saves every change as a draft. This page is about which one fits your situation.

The short version: If you work in a coding agent with Studio open and want the YAML validated as it is written, use Microsoft’s. FlowStudio does six things Microsoft’s cannot do today:
  • It works from ChatGPT, Claude, Copilot Studio or Cowork, including ChatGPT on your phone. Microsoft’s runs as a plugin in a coding agent on your computer.
  • It works with Power Apps Studio closed. Microsoft’s needs Studio open, with coauthoring on, for the whole session.
  • It adds SharePoint, Excel, SQL and Dataverse data sources itself. With Microsoft’s, you add them in Studio.
  • It saves every change as a draft version and publishes with one call. With Microsoft’s, you save and publish in Studio.
  • It works on several apps at once. Microsoft’s is set up for one app, and you run its setup again to switch.
  • It fixes the flows behind the app over the same connection. Microsoft’s flow tool is a separate plugin, FlowAgent.
Both can sit in one coding agent.

What each one is

Microsoft’s Canvas Authoring MCP server has been on NuGet since March 2026. Its Microsoft Learn guide, Create and edit canvas apps with AI code generation tools, came out on 27 August, its first version without a preview label on 31 August, and Microsoft announced it as generally available on 1 September. 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 Power Apps canvas app MCP: build and edit apps with your AI agent.

We ran the same tasks through both on 25 October 2026. Both work.

Side by side

We checked Microsoft’s details on 31 October 2026, against its Microsoft Learn guide (dated 27 August 2026, last updated 13 October 2026) and its NuGet package. Microsoft ships fast. Check theirs before you decide.

Dimension Microsoft Canvas Authoring MCP server FlowStudio MCP canvas tools
Who it is for People who build in a coding agent, with Studio open beside it Makers and developers, whether or not they use a coding agent
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
Where changes go Generated .pa.yaml is synced into the live coauthoring session; you publish from Studio Edits go to a server-side session, a push saves a draft version, publish is a separate call
Checking formulas Checks the generated YAML on every compile and reports errors for the agent to fix 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, and the agent merges and pushes again
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 On NuGet since March 2026; generally available since 1 September 2026. Guide on Microsoft Learn dated 27 August 2026, updated 13 October. 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 as it writes. FlowStudio’s pushes a draft from a hosted server and lets you check it before anyone sees it.

The difference in practice

Video: John Liu on why we built a canvas MCP when Microsoft has one (2 min)

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 if a maker changes the app while the session is open, the push stops until the agent has merged their changes. 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.

An error in the session, or a warning and a draft

Microsoft’s checks the YAML every time it compiles and reports a bad formula as an error, and its skill has the agent fix it and compile again. FlowStudio’s formula check runs Microsoft’s open-source Power Fx checker and reports a bad formula as a warning, and the draft is where you see the result before anyone else does. Neither refuses a bad formula outright. In our test on 25 October 2026, Microsoft’s synced the failing YAML into the open Studio session, and FlowStudio’s would have pushed it as a draft.

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 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 every change, to a new app or an existing one, saved as a draft you check before users see it
  • Someone else may be editing the app, and you want the agent to stop and merge their changes rather than write over them
  • 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 save in Studio writes Studio’s copy over the latest version, and a FlowStudio push stops when the app has moved, so the agent can merge before it pushes again.

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. We recommend closing Studio while the agent works. A Studio tab opened before the push still holds the old copy, and saving it writes that copy over the draft. If someone has to keep Studio open, the agent can take the app’s edit lease for the push; their tab goes read-only until they reload it. Reopen Studio afterwards to look at the draft.

What happens if someone changes the app while FlowStudio is working on it?

FlowStudio edits its own copy of the app on the server and pushes all its changes as one new draft version. Before the push, it checks whether the app has moved since it started: someone saved in Studio, Studio autosaved, or another agent pushed. If it has, the push stops and nothing is written. The agent compares the version it started from, the newer one, and its own edits. Screens only the other person changed keep their changes. Where both changed the same screen, the agent is told which one, so it can bring the other person’s changes into its own. Then it pushes again on top of the newer version. The result is still a draft, so you check it before anyone publishes.

Can FlowStudio work on more than one app at a time?

Yes. The FlowStudio server keeps a separate session for each app, so the agent is not tied to the one app Studio has open. It can read, create and change several canvas apps at once, and read one app while it changes another, for example to see how a screen is built before it builds a similar one in a new app.

Which one checks Power Fx formulas?

Both, differently. Microsoft’s checks the generated YAML on every compile and reports problems as errors for the agent to fix. 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: Power Apps canvas app MCP: build and edit 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.