Skip to content

Copilot Studio for Power Automate with Flow Studio MCP

Wire Flow Studio MCP into a Microsoft Copilot Studio agent so your AI agent can read, debug, build, and govern Power Automate cloud flows. One install at the agent level, then every M365 Copilot user in your tenant gets access from Teams chat or m365.cloud.microsoft.

Copilot Studio Power Automate setup

Copilot Studio Power Automate works through Flow Studio MCP, an independent MCP server. Add an MCP server to your Copilot Studio agent in the portal Tools tab, paste your API key, publish to Teams or M365 Copilot. Every M365 Copilot user in your tenant gets access with no per-user install.

For the full agent install matrix across Claude, GitHub Copilot, Codex, and other agents, see Install Flow Studio MCP for Power Automate.

How Microsoft Copilot Studio works with Power Automate

Microsoft Copilot Studio is the Microsoft platform for building AI agents that publish to Microsoft Teams, Microsoft 365 Copilot, or a custom web channel. Out of the box, Copilot Studio agents can call Power Automate flows as actions and trigger them on user input. What Copilot Studio cannot do natively: read run history, inspect action-level inputs and outputs, debug failed runs, modify flow definitions, or build new flows from natural language.

Flow Studio MCP is an MCP server for Power Automate that fills that gap. Copilot Studio supports the Model Context Protocol natively as a tool type. You add Flow Studio MCP as an MCP server in the agent Tools tab, publish, and your agent gains 30+ Power Automate tools: list_live_flows, get_live_flow_run_action_outputs, update_live_flow, describe_live_connector, and more.

The deployment model is the killer feature: one install at the agent level reaches every user. You wire Flow Studio MCP in once, publish, and every M365 Copilot user in your tenant can ask their agent to debug, build, or govern Power Automate flows from Teams chat or m365.cloud.microsoft, without installing anything themselves.

Install Flow Studio MCP in Copilot Studio

Five steps in the Copilot Studio portal. No code, no JSON, no config files.

  1. Get an API key. Sign up at mcp.flowstudio.app. Grant Power Automate and Power Apps permissions in the dashboard. Copy your API key. Free evaluation: 100 calls over 21 days, no credit card.
  2. Open your Copilot Studio agent. Go to copilotstudio.microsoft.com. Create a new agent or open an existing one. Click the Tools tab.
  3. Add an MCP server. Click + Add a tool. In the Create new row, click the Model Context Protocol card.
  4. Fill the connection form. Use these exact values:
    • Server URL: https://mcp.flowstudio.app/mcp
    • Authentication: API key
    • Type: Header
    • Header name: x-api-key (lowercase, with the hyphen, this is the most common setup mistake)
    Click Create. When asked to Create new connection, paste your API key.

    5. Copilot Studio Add a Model Context Protocol server form filled in with Server name Flow Studio MCP, Server URL https://mcp.flowstudio.app/mcp, Authentication API key, Type Header, Header name x-api-key

  5. Publish. Click Publish in the top right. Pick the Microsoft Teams and Microsoft 365 Copilot channels. Done.

Common setup mistake: using the Bearer token auth field. Copilot Studio offers it, but Flow Studio MCP rejects Authorization: Bearer with HTTP 401. Always use Header authentication type with header name x-api-key.

Sample prompts you can ask your Copilot Studio agent
  • "List my Power Automate flows in the Default environment"
  • "Why did my Invoice Approval flow fail this morning? Read the latest run."
  • "Build a Power Automate flow that triggers on new SharePoint list items in my Issues list and posts a card to the #issues Teams channel"
  • "Show me action-level inputs and outputs of the most recent HR Sync run"
  • "Resubmit the failed run from yesterday with the same trigger payload"
  • "Find all Power Automate flows owned by users who left the company" (requires governance skill plus Pro+ tier)
What your agent can do once Flow Studio MCP is connected
You ask the agent What the agent does
"Why is this flow failing?"Reads run history, drills into the failed action, returns the actual error message and inputs.
"Fix the expression error and redeploy"Patches the Workflow Definition Language JSON and calls update_live_flow to deploy. One round-trip.
"Build a flow that..."Discovers connections, constructs the flow, deploys it, all in one round-trip.
"Show me the impact of deleting this flow"Reads governance metadata: downstream users, last run, owner. Recommends safe vs risky.
"Audit our flow estate"Queries the Flow Studio governance store for orphaned flows, inactive makers, and connector-by-connector usage across the tenant. Pro+ tier.
Multi-tenant deployment notes

Each Flow Studio MCP API key is scoped to one Microsoft Entra tenant. If your Copilot Studio agent serves multiple tenants (uncommon, but possible for ISVs), you need one Flow Studio MCP subscription per tenant and one MCP server entry per tenant in your agent. The agent uses the appropriate connection at runtime based on the user's tenant.

For a single-tenant deployment (the usual case), one API key covers every M365 Copilot user in your tenant. Pricing is per workspace, not per user.

Frequently asked questions
How do I connect Microsoft Copilot Studio to Power Automate cloud flows?

Install Flow Studio MCP, an MCP server for Power Automate, into your Copilot Studio agent. Open copilotstudio.microsoft.com, go to the Tools tab on your agent, click + Add a tool, then Model Context Protocol. Set Server URL to https://mcp.flowstudio.app/mcp, Authentication to API key, Type to Header, Header name to x-api-key. Paste your API key, click Create, then Publish to Microsoft Teams or M365 Copilot.

Does Copilot Studio support Power Automate cloud flow inspection out of the box?

Copilot Studio agents can call Power Automate flows as actions, but cannot read action-level run history, inspect failed runs, or modify flow definitions. Flow Studio MCP adds 30+ Power Automate tools to any Copilot Studio agent: read run history, inspect inputs and outputs at every action level, build new flows, debug failed runs, and govern flows tenant-wide.

Once I install Flow Studio MCP, do my users need to install anything?

No. Flow Studio MCP installs at the Copilot Studio agent level, not per user. Once you publish the agent to Microsoft Teams or M365 Copilot, every M365 Copilot user in your tenant can use the Power Automate tools from Teams chat or m365.cloud.microsoft, with no per-user install.

Can my Copilot Studio agent build a new Power Automate flow on demand?

Yes. With the power-automate-build skill installed, your agent discovers connections via list_live_connections, resolves dynamic dropdown values via describe_live_connector and get_live_dynamic_options, constructs the Workflow Definition Language JSON, then deploys via update_live_flow. The flow appears in Power Automate already deployed.

What is the most common Copilot Studio MCP setup mistake?

Using Authorization: Bearer instead of x-api-key. Flow Studio MCP requires the x-api-key header (lowercase, with the hyphen). Copilot Studio offers a Bearer token field which sends Authorization: Bearer. Flow Studio rejects this with HTTP 401. Use the Header authentication type, name x-api-key, paste your JWT into the value.

Is Flow Studio MCP affiliated with Microsoft Copilot Studio?

No. Flow Studio MCP is an independent product made by Flow Studio. It is not affiliated with, endorsed by, or sponsored by Microsoft Corporation. It uses the open Model Context Protocol that Microsoft Copilot Studio supports natively, and the Power Platform API to talk to Power Automate on your behalf using your API key.

Next steps

Flow Studio is an independent product and is not affiliated with, endorsed by, or sponsored by Microsoft Corporation. Microsoft, Copilot Studio, Power Automate, Power Platform, Microsoft 365, and Copilot are trademarks of the Microsoft group of companies.