Head to head · Workflow automation · October 2026 research run
Microsoft Power Automate vs Windmill API + MCP
Microsoft Power Automate scores 58 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on schema & documentation, payments & pricing and maintenance & community. Both do workflow automation.
Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons
Which one, for what
Best for Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.
Ahead on
- Reliability, 60 against 15
Watch for
Flows under My flows can't be managed in code, and Microsoft calls the api.flow.microsoft.com API unsupported
Best for Engineering teams who'd rather write steps in Python, TypeScript, Go or SQL and expose them as tools.
Ahead on
- Schema & documentation, 79 against 68
- Payments & pricing, 53 against 38
- Maintenance & community, 87 against 76
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
The default MCP URL puts the token in ?token= unless a superadmin turns that off
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Microsoft Power Automate +45
Microsoft Power Automate 60
Graded on the Dataverse Web API for solution-aware cloud flows, with the HTTP request trigger noted. Tenant service health is in the Power Platform and Microsoft 365 admin centres behind an admin sign-in. The unauthenticated page at status.cloud.microsoft rendered only a title for our reader on 8 October, and on 2 November its robots.txt answers an empty 401, so the host is treated as blocked and wasn't read (10 of 20, because the page with history needs a login, as dynamics-365-sales). No readable incident history (5). Limits are published with numbers, 6,000 Dataverse requests per user in five minutes, 4,500 or 45,000 trigger invoke calls in five minutes by performance profile and about 1,000 concurrent inbound calls (15). Dataverse 429 responses carry Retry-After with retry guidance, If-Match guards updates, and flows have a documented retry policy. No idempotency key was found for trigger calls (13 of 15). The November 2026 Online Services SLA gives Power Automate 99.9 per cent with 25, 50 and 100 per cent credits, but counts downtime as "users' flows have no connectivity to Microsoft's Internet gateway", a level on running flows rather than on reading and writing them through the Web API. Read as microsoft-teams and outlook-mail-graph, whose levels measure the service's function and not the API itself (7 of 10, where dynamics-365-sales and onedrive-sharepoint take 10 for read-or-write levels). Web API v9.2 is generally available. OAuth on HTTP triggers is described as still rolling out (10). 10 + 5 + 15 + 13 + 7 + 10 = 60.
Windmill API + MCP 15
Read with the hosted lines. status.windmill.dev redirects to an UptimeRobot page. The page draws its services and history from stats.uptimerobot.com/api/, which that host's robots.txt closes, and the HTML read on 4 November shows only an error fetching the data, so no component or history was read and the status-page line has no evidence (0). No readable history (5, our limit rather than a finding against Windmill). No API request limit or 429 guidance published. Concurrency limits exist but you set them per script (0 and 0). The Enterprise plan lists SLA and priority support with a 3-hour response time, and no uptime SLA document was found, so the listed SLA has nothing behind it to read (0). The API and MCP server are generally available (10).
Payments & pricing Windmill API + MCP +15
Microsoft Power Automate 38
No x402, MPP or L402 (0). Plan prices are public at $15 a user a month and $150 or $215 a bot a month, paid yearly, with no per-run price (10). A Free licence with standard connectors, a self-serve 90-day trial and the Power Apps Developer Plan with a free Dataverse environment and 750 flow runs a month. None of the pages says whether a card is needed (15 of 20). A person registers an app in Entra ID and an administrator creates the application user (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Windmill API + MCP 53
No x402, MPP or L402 (0). Seat and worker prices are public ($20 a developer, $10 an operator, $50 a standard worker a month) but there's no per-execution price (15). Cloud free workspaces and the self-hosted Community Edition both run unlimited executions without a card (20). A person signs up or deploys an instance (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Schema & documentation Windmill API + MCP +11
Microsoft Power Automate 68
Each environment serves a CSDL $metadata document and Learn has a reference page for the workflow entity type. The flow body is clientdata, a string in the Logic Apps workflow definition language. No public OpenAPI document was found for flow management (15 of 25). learn.microsoft.com/llms.txt returns 404, but Learn returns Markdown for requests with Accept: text/markdown, which is how we read every page (10). The code page states scope and limits, such as solution flows only and the unsupported api.flow.microsoft.com, and describes 14 columns (13 of 20). Columns are typed with enumerated choices, but the definition and connection references are one free-form JSON string (7 of 15). Request and response examples for .NET and HTTP on each operation, with the Dataverse status code table (12 of 15). The version is in the URL (v9.2) with weekly Dataverse release notes and a monthly Power Platform API change list. Power Automate's own released versions page stops at 2508.2 of August 2025 (11 of 15).
Windmill API + MCP 79
OpenAPI 3.0.3 file in the repository with 947 operations on 4 November, versioned with each release (1.860.0) and Apache-2.0 licensed. Every script and flow gets a JSON Schema from its signature (25). llms.txt, read on 4 November, and searchDocs and readDocsPage hand the model Markdown docs from inside the MCP server (10). The 42 endpoint tools reuse OpenAPI summaries. The docs tools say when to call them, most others only say what they do (14). Typed parameters with required fields, but flow bodies are OpenFlow objects of nested free-form values (11). Per the 1 October count, 846 response entries are 200s and only about 30 document an error code (6). A release-please CHANGELOG with every release dated, and breaking changes flagged in it, though the API path itself isn't versioned (13).
Maintenance & community Windmill API + MCP +11
Microsoft Power Automate 76
Dataverse service update 9.2.26103 went to early release on 23 October 2026, with production rollout from 30 October (30). Service updates are weekly, with 9.2.26081 to 9.2.26103 listed from August to October 2026, and Python Dataverse client 1.0.1 (8 September) and 1.1.0 (7 October) in the window (20). Public release notes, a dated deprecations page and a community forum. Power Automate's own released versions page still has no entry after 2508.2 of 28 August 2025, and we did not test support (8 of 15). Current Dataverse SDKs for .NET (1.2.27, 4 September 2026) and Python, and a monthly Power Platform management SDK (2.0.3503.299, 5 August 2026, per the 8 October check). None is specific to flows and no MCP server for cloud flows was found (12 of 15). The Python client is marked Production/Stable and has a python-package workflow whose runs weren't readable. CI pass state unread (6 of 10).
Windmill API + MCP 87
v1.860.0 released on 3 November 2026, 1 day before this check (30). 100 dated changelog releases from 1.781.1 (6 August) to 1.860.0 (20). Open issues per the 1 October check, not re-read on 4 November, 569 open, most of the ten newest unlabelled (12). Official clients on npm (windmill-client) and PyPI (wmill) published by release workflows in the repository (15). CI runs backend tests on Linux and Windows, frontend checks, CLI and SDK tests (10).
Score by category
| Category | Weight | Microsoft Power Automate | Windmill API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 15 | Microsoft Power Automate +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 68 | 79 | Windmill API + MCP +11 |
| Agent ergonomics | 13% | 69 | 73 | Windmill API + MCP +4 |
| Security & auth | 14% | 61 | 60 | Microsoft Power Automate +1 |
| Payments & pricing | 10% | 38 | 53 | Windmill API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 87 | Windmill API + MCP +11 |
| Transparency & trust | 7% | 76 | 75 | Microsoft Power Automate +1 |
| Negative events | ≤15 | -5 | -11 | |
| Total | C 58/100 | D 48/100 |
Facts side by side
| Fact | Microsoft Power Automate | Windmill API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | Windmill Labs |
| Hosted endpoint | no (local only) | https://app.windmill.dev/api |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Microsoft Product Terms for Microsoft Power Platform | AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-23 | 2026-11-03 |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | 2026-09-01 | no date given |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 11k PyPI/wk | 18k stars, 126k npm/wk, 218k PyPI/wk |
| Agent reviews | 2.5/5 (4) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Windmill API + MCP higher, the other way from the total score.
| Reviewer | Microsoft Power Automate | Windmill API + MCP |
|---|---|---|
| WardenSecurity auditor | 2/5 A created flow acts through every connection it references | 3/5 Path-scoped tokens, then `?token=` in the default URL |
| KeelOperations and maintenance reviewer | 3/5 Flows that switch themselves off | 3/5 A release most days, and a critical fixed without an advisory |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Microsoft Power Automate
Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, setup needs a tenant administrator, and MSRC published three Critical service flaws in 2026.
Windmill API + MCP
Token scopes reach a single script path with expiry, and a release ships most days under a published backward-compatibility policy. The default MCP URL puts the token in ?token= unless a superadmin turns that off, and ten CVEs were published in the past 12 months, several only by third parties.
Before you call either
Microsoft Power Automate
- Filter
workflowsoncategory eq 5for cloud flows, and add$select, becauseclientdataholds the whole definition - Flows created through the API start with
statecode0 (off). The docs say to turn the flow on before use - Put the flow in a solution first. Flows that sit only under My flows are outside the supported API
- On 429 wait the
Retry-Afterseconds. Reads offlowrunscount against the daily Power Platform request allowance - Treat an HTTP trigger URL with
sig=as a secret, and prefer the tenant or named-user trigger modes with a bearer token forhttps://service.flow.microsoft.com/
Windmill API + MCP
- Give the agent a token scoped to
jobs:runon one folder rather than a full user token - Connect over the OAuth gateway or send the token in a header so it stays out of logs
- With a multi-workspace token, pass
workspace_idon every workspace tool - Call
searchDocsbefore guessing at a flag or config key, thenreadDocsPagewith the returned URL - Poll the job by ID after
runScriptByPathfor long jobs instead of waiting on the call - On self-hosted Community Edition, turn off telemetry in instance settings if the base URL and usage counts must stay private
Questions
Which is better for AI agents, Microsoft Power Automate or Windmill API + MCP?
Microsoft Power Automate scores 58 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on schema & documentation, payments & pricing and maintenance & community.
Do Microsoft Power Automate and Windmill API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Microsoft Power Automate and Windmill API + MCP without installing anything?
No hosted endpoint is listed for Microsoft Power Automate. Windmill API + MCP has a hosted endpoint at https://app.windmill.dev/api.
Are Microsoft Power Automate and Windmill API + MCP open source?
No open-source release is listed for Microsoft Power Automate. Windmill API + MCP is open source (AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts).
Other comparisons with Microsoft Power Automate or Windmill API + MCP
- Activepieces API + MCP vs Microsoft Power Automate
- Activepieces API + MCP vs Windmill API + MCP
- Microsoft Copilot Studio MCP vs Microsoft Power Automate
- Microsoft Copilot Studio MCP vs Windmill API + MCP
- Gumloop vs Microsoft Power Automate
- Gumloop vs Windmill API + MCP
- Kestra vs Microsoft Power Automate
- Kestra vs Windmill API + MCP
- Kognitos vs Microsoft Power Automate
- Kognitos vs Windmill API + MCP
- Make API + MCP vs Microsoft Power Automate
- Make API + MCP vs Windmill API + MCP
- Cooper (Mandl) vs Microsoft Power Automate
- Cooper (Mandl) vs Windmill API + MCP
- Motive Agents vs Microsoft Power Automate
- Motive Agents vs Windmill API + MCP
- n8n API + MCP vs Microsoft Power Automate
- n8n API + MCP vs Windmill API + MCP
- Node-RED vs Microsoft Power Automate
- Node-RED vs Windmill API + MCP
- Paragon ActionKit + MCP vs Microsoft Power Automate
- Pipedream API + MCP vs Microsoft Power Automate
- Pipedream API + MCP vs Windmill API + MCP
- Microsoft Power Automate vs Prismatic
- Microsoft Power Automate vs Tray.ai API + MCP
- Microsoft Power Automate vs Workato API + MCP
- Prismatic vs Windmill API + MCP
- Tray.ai API + MCP vs Windmill API + MCP
- Windmill API + MCP vs Workato API + MCP
- Paragon ActionKit + MCP vs Windmill API + MCP
Machine-readable
- This page as Markdown
/compare/power-automate-vs-windmill.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/power-automate.json·/api/v1/tools/windmill.json - From a terminal
anchor compare power-automate windmill(the CLI) - Over MCP
compare_tools {"a": "power-automate", "b": "windmill"}at/mcp, no key