Claude + Power Automate: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude Power Automate connector, and Microsoft ships no general-purpose Power Automate MCP server. That’s verified against Microsoft’s official MCP catalog and its own MCP server connector reference: what exists officially in Power Platform is a Dataverse MCP server (Dataverse is in Claude’s directory), a Power Apps MCP in preview, and a local pac CLI server for developers — none of which lets Claude list or run your cloud flows. The interesting twist runs the other way: Claude models are pickable inside Copilot Studio and enabled across Power Platform, per Microsoft’s subprocessor doc. And as always, anything you do wire up only works inside a conversation you start.
Here’s what actually connects today, the one real external hook Power Automate offers, where the limits bite, and the case for skipping the flow-builder entirely.
What actually exists (and what’s third-party)
- Official Power Automate MCP server: none. The closest official pieces are the Dataverse MCP server (cloud-flow definitions live in Dataverse) and a narrow Process Mining MCP server in preview.
- Flow Studio MCP (mcp.flowstudio.app) — a well-regarded third-party remote MCP by John Liu with 30+ Power Automate tools: list flows, inspect run history, action-level debugging. Usable from Claude as a custom connector, genuinely handy for admins and makers — just be clear it’s community-built, not Microsoft’s.
- Claude inside Copilot Studio — since January 2026 Anthropic models are on by default across M365 Copilot, Copilot Studio, and Power Platform in commercial cloud. Copilot Studio agents can consume MCP servers as tools (GA since May 2025), and flows attach to agents as agent flows. That’s Claude powering agents inside Microsoft’s stack — not your claude.ai account driving your flows.
The one real external hook: the HTTP trigger
If you want Claude — or anything outside Microsoft’s walls — to start a flow, Power Automate offers exactly one sanctioned mechanism: the “When an HTTP request is received” trigger. The flow mints a URL; any tool that can POST JSON can fire it. Two catches:
- It’s a premium trigger — you need Power Automate Premium (~$15/user/month) or a per-flow plan.
- It only works for flows built with that trigger. There’s no API to generically say “run flow X now.” The Power Automate Management connector can list, enable, and disable flows — and its “start flow” action is a famous trap: it enables a flow, it doesn’t execute a run.
So the honest architecture is: build a flow with an HTTP trigger, then have your assistant POST to it with a payload. Since 2024 you can require Entra OAuth on the trigger instead of relying on the SAS-signed URL alone.
The limits that actually matter
- Nothing official end-to-end. No directory connector, no Microsoft MCP server for flows. Flow Studio MCP is solid but third-party.
- Claude can’t run arbitrary flows. Only HTTP-trigger (or agent-trigger) flows are externally invokable. Everything else fires on its own events and schedules.
- No triggers on Claude’s side. Even wired to Flow Studio MCP, Claude only acts inside a conversation you start. It won’t notice a failed flow run at 3am or kick off your onboarding flow when a calendar event lands.
- You’re still building flows. The deeper issue: Power Automate’s model is drag-and-drop flow construction — triggers, actions, connections, error handling. Copilot in Power Automate can draft a flow from a description, but you still own the canvas, the premium licensing, and the debugging.
If you want Power Automate work that runs on its own: Carly
Here’s the reframe worth considering: most people searching “Claude Power Automate” don’t want Claude bolted onto a flow-builder — they want automations they can describe in plain English that then run by themselves. That’s exactly what Carly is: an AI executive assistant that is the automation layer, no canvas required.
Instead of building a flow, you tell Carly “when a contract request lands in my inbox, pull the details, add a task, and email the summary to legal” — it interviews you, then builds and runs the workflow in the cloud. And where you already have Power Automate flows you love, Carly works alongside them via the platform’s real APIs — connect your Microsoft stack and paste any API credentials on carlyassistant.com/integrations:
- Fire your existing HTTP-trigger flows — Carly can POST a JSON payload to a flow’s trigger URL as a workflow step, so an email, calendar event, or CRM change anywhere in your stack can kick off a Teams approval chain you’ve already built.
- Morning flow-failure sweep — flow runs are Dataverse-backed; Carly checks run history each morning and sends one line per failure to each owner, instead of failures dying silently.
- Replace the flow entirely — inbox triage, meeting scheduling, CRM updates, follow-up sequences: describe them once, Carly runs them 24/7 without a premium-trigger license or a canvas to maintain.
- No-code setup — plain English in, working automation out. No connectors to configure, no run-after conditions to debug.
- Actually sends — drafts and sends email across Gmail and Outlook, updates records, manages tasks.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (with Power Automate today) | Carly | |
|---|---|---|
| List / inspect flows | Yes, via third-party Flow Studio MCP | Not needed — Carly is the automation layer |
| Run an arbitrary flow on demand | No (HTTP-trigger flows only) | Fires HTTP-trigger flows as workflow steps |
| Build automation from plain English | Drafts flows via Copilot; you finish the canvas | Yes — describe it, Carly builds and runs it |
| Acts on triggers / events | No (conversation-only) | Yes, 24/7 |
| Runs while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Extra licensing for external triggers | Premium (~$15/user/mo) | None — included |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude next to Power Automate is a consultant who can read your flows. Carly is the assistant that makes most of those flows unnecessary.
Frequently Asked Questions
Does Claude work with Power Automate?
Not officially. There’s no Claude directory connector and no Microsoft-built Power Automate MCP server (Microsoft’s MCP catalog confirms it). The workable routes: the third-party Flow Studio MCP for listing flows and debugging runs, and POSTing to premium HTTP-trigger flows. Separately, Claude models run inside Copilot Studio and Power Platform — the reverse direction.
Can Claude run one of my flows?
Only if the flow was built with the premium “When an HTTP request is received” trigger — then anything, Claude tooling included, can POST to its URL. There is no API to execute an arbitrary flow; the Management connector’s “start flow” action merely enables a flow.
Isn’t Claude already in Power Platform?
As a model, yes. Since January 2026, Anthropic models are on by default in Microsoft 365 Copilot, Copilot Studio, and Power Platform (commercial cloud; EU/UK opt-in since April 2026). Copilot Studio agents can call flows as agent flows. None of that connects your claude.ai account to your flows.
Do I even need Power Automate if I use Carly?
Often not. Carly builds and runs trigger-based workflows from a plain-English description — no canvas, no premium trigger licensing — and for flows you keep, Carly can fire your HTTP-trigger flows as steps in a larger workflow. AI agents start at $35/month.
More: Claude + Power BI · Claude + Zapier · Claude + Outlook · Claude + Teams · Claude connectors · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
