Claude for Power Automate with Flow Studio MCP
Connect Claude to Power Automate so you can build, debug, and operate cloud flows from a chat instead of the portal. Works with Claude Code (CLI plus VS Code extension), Claude Desktop, and any other Anthropic Claude surface that supports the Model Context Protocol.
Claude Power Automate setup
Claude Power Automate works through Flow Studio MCP, an independent MCP server. Install via the VS Code extension for Claude Code, the Claude CLI plugin, or the Claude Desktop config. All three paths reach the same 30+ Power Automate tools and 5 bundled skill recipes.
For the full agent install matrix across Copilot Studio, Codex, and other agents, see Install Flow Studio MCP for Power Automate.
How Claude works with Power Automate
Claude does not have native access to Microsoft Power Automate. You give it access by installing Flow Studio MCP, an MCP server for Power Automate. Once Flow Studio MCP is registered with Claude, Claude can call 30+ Power Automate tools: list flows, read run history, inspect action-level inputs and outputs, build new flows, fix broken ones, and apply governance metadata.
The same MCP connection works across Claude Code (the Anthropic Claude CLI and the VS Code extension), Claude Desktop on Windows and macOS, and any other Claude surface that supports MCP. One API key, one config block, available everywhere Claude runs.
Install Flow Studio MCP for Claude
Three install paths, all first-class. Pick whichever fits your workflow.
Option 1: Claude Code via VS Code extension (one-click)
Install the Power Automate MCP for Claude Code extension from the VS Code Marketplace. Cursor, VSCodium, and Windsurf users: install from Open VSX.
- Install the extension from the Marketplace or Open VSX.
- Get an API key at mcp.flowstudio.app. Free to start.
- In VS Code, run the command Flow Studio (Claude): Add Tenant Connection. Enter a tenant name and paste your API key.
- Reload the window. Claude Code in VS Code, in the terminal, and on Desktop all pick up the new MCP server and the 5 bundled skills (
power-automate-mcp,power-automate-debug,power-automate-build,power-automate-monitoring,power-automate-governance).
Option 2: Claude CLI plugin (no editor required)
Same connection and same skills as Option 1, installed from the terminal. Use this if you do not run a supported editor.
git clone https://github.com/ninihen1/power-automate-mcp-skills.git claude --plugin-dir ./power-automate-mcp-skills
Then connect the MCP server:
claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \ --header "x-api-key: YOUR_API_KEY"
Option 3: Claude Desktop (Windows or macOS)
Claude Desktop reaches the remote Flow Studio MCP server via the mcp-remote bridge package. Requires Node.js installed on your machine.
Open the Claude Desktop config file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the following:
{
"mcpServers": {
"flowstudio": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://mcp.flowstudio.app/mcp",
"--header",
"x-api-key: YOUR_API_KEY",
"--header",
"User-Agent: FlowStudio-MCP/1.0"
]
}
}
}
Restart Claude Desktop. The Flow Studio MCP tools become available immediately.
Sample prompts you can copy
- "List my Power Automate flows in the Default environment"
- "Why is my HR Sync flow failing? Read the latest run and find the root cause."
- "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 the action-level inputs and outputs of the latest Invoice Processing run"
- "Resubmit the failed run from yesterday with the same trigger payload"
What you can do once Claude is connected
| You say to Claude | What Claude 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. |
| "Build a flow that..." | Discovers connections, constructs the flow, deploys it, all in one round-trip. |
| "What is the impact if I delete this flow?" | Reads governance metadata (downstream users, last run, owner) before recommending. |
| "Show me all flows owned by John" | Queries the Flow Studio governance store for flows by owner across the tenant. |
Next steps
- Full Flow Studio MCP setup guide for all agents (Claude, GitHub Copilot, Microsoft Copilot Studio, OpenAI Codex, and others)
- Browse the 30+ tools Claude can call via Flow Studio MCP
- Install the 5 skill bundles for build, debug, monitor, discover, governance
- Worked example: build a Power Automate flow with an AI agent
- Start your free evaluation: 100 calls, 21 days, no credit card
Flow Studio is an independent product and is not affiliated with, endorsed by, or sponsored by Anthropic or Microsoft Corporation. Claude is a trademark of Anthropic. Microsoft, Power Automate, Power Platform, and Copilot are trademarks of the Microsoft group of companies.