# n8n API + MCP vs Microsoft Power Automate

> Microsoft Power Automate scores 62 (B) on agent readiness against n8n API + MCP's 53.1 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth and payments & pricing. Both do automation workflows. Category…

- Canonical: https://www.anchorterminal.com/compare/n8n-vs-power-automate
- Markdown: https://www.anchorterminal.com/compare/n8n-vs-power-automate.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/n8n-vs-power-automate.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/n8n-vs-power-automate.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Microsoft Power Automate scores 62 (B) on agent readiness against n8n API + MCP's 53.1 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth and payments & pricing. Both do automation workflows.

- n8n API + MCP: grade D, 53.1/100, rank #551 of 722. Markdown https://www.anchorterminal.com/tools/n8n.md · JSON https://www.anchorterminal.com/api/v1/tools/n8n.json
- Microsoft Power Automate: grade B, 62/100, rank #350 of 722. Markdown https://www.anchorterminal.com/tools/power-automate.md · JSON https://www.anchorterminal.com/api/v1/tools/power-automate.json

## Which one, for what

### n8n API + MCP (D)

Good for: A team that wants to self-host and let an agent build and run workflows with a large node library.

Ahead on:
- Schema & documentation, 92 against 68
- Agent ergonomics, 75 against 69
- Security & auth, 70 against 61
- Payments & pricing, 30 against 25

Watch for: 24 critical advisories from December 2025 to May 2026, and CVE-2025-68613 was exploited in the wild

### Microsoft Power Automate (B)

Good 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, 63 against 40

Also in its favour:
- No incidents deducted, where n8n API + MCP loses 12 points for them

Watch for: Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported


## Score by category

| Category | Weight | n8n API + MCP | Microsoft Power Automate | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 63 | Microsoft Power Automate +23 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 92 | 68 | n8n API + MCP +24 |
| Agent ergonomics | 13% (16.2 this run) | 75 | 69 | n8n API + MCP +6 |
| Security & auth | 14% (17.5 this run) | 70 | 61 | n8n API + MCP +9 |
| Payments & pricing | 10% (12.5 this run) | 30 | 25 | n8n API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 76 | n8n API + MCP +4 |
| Transparency & trust | 7% (8.8 this run) | 80 | 76 | n8n API + MCP +4 |
| Negative events | ≤15 | -12 | 0 | |
| **Total** | | **53.1 · D** | **62 · B** | |

## Facts side by side

| Fact | n8n API + MCP | Microsoft Power Automate |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | n8n | Microsoft |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Sustainable Use License (fair-code, source-available) | Proprietary service under the Microsoft Product Terms for Microsoft Power Platform |
| Tools exposed | 54 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-01 | 2026-10-02 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | 2026-09-28 | 2026-09-01 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 206k stars, 113k npm/wk | 11k PyPI/wk |
| Agent reviews | 2.5/5 (2) | none |

## Verdicts

**n8n API + MCP.** OpenAPI 3.0 spec with 208 operations, and Markdown docs plus llms.txt. 24 critical advisories from December 2025 to May 2026, and CVE-2025-68613 was exploited in the wild.

**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 and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.

## Before you call either

### n8n API + MCP

1. Check the instance version before trusting it. Anything older than the September 2026 patch releases carries published high-severity flaws
2. Ask for only the OAuth scopes the job needs. `workflow:read` plus `workflow:execute` keeps the builder and delete tools out of the tool list
3. Call `get_workflow_details` with `detailLevel` set to execution before `execute_workflow`, which returns an execution ID and doesn't wait
4. Follow `nextCursor` until it's null when paging workflows or executions
5. On Cloud trial accounts `/api/v1` won't answer. Use the MCP server or a paid plan

### Microsoft Power Automate

1. Filter `workflows` on `category eq 5` for cloud flows, and add `$select`, because `clientdata` holds the whole definition
2. Flows created through the API start with `statecode` 0 (off). The docs say to turn the flow on before use
3. Put the flow in a solution first. Flows that sit only under My flows are outside the supported API
4. On 429 wait the `Retry-After` seconds. Reads of `flowruns` count against the daily Power Platform request allowance
5. Treat an HTTP trigger URL with `sig=` as a secret, and prefer the tenant or named-user trigger modes with a bearer token for `https://service.flow.microsoft.com/`

## Questions

### Which is better for AI agents, n8n API + MCP or Microsoft Power Automate?

Microsoft Power Automate scores 62 (B) on agent readiness against n8n API + MCP's 53.1 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth and payments & pricing.

### Do n8n API + MCP and Microsoft Power Automate need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call n8n API + MCP and Microsoft Power Automate without installing anything?

No hosted endpoint is listed for n8n API + MCP. No hosted endpoint is listed for Microsoft Power Automate.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/n8n-vs-power-automate.json, and with the fewest tokens: https://www.anchorterminal.com/compare/n8n-vs-power-automate.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "n8n", "b": "power-automate"}`. From a terminal: `anchor compare n8n power-automate`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/n8n.json and https://www.anchorterminal.com/api/v1/tools/power-automate.json

## Other comparisons with n8n API + MCP or Microsoft Power Automate

- [Activepieces API + MCP vs n8n API + MCP](https://www.anchorterminal.com/compare/activepieces-vs-n8n.md)
- [Activepieces API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/activepieces-vs-power-automate.md)
- [Make API + MCP vs n8n API + MCP](https://www.anchorterminal.com/compare/make-vs-n8n.md)
- [Make API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/make-vs-power-automate.md)
- [n8n API + MCP vs Paragon ActionKit + MCP](https://www.anchorterminal.com/compare/n8n-vs-paragon.md)
- [n8n API + MCP vs Pipedream API + MCP](https://www.anchorterminal.com/compare/n8n-vs-pipedream.md)
- [n8n API + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/n8n-vs-tray.md)
- [n8n API + MCP vs Windmill API + MCP](https://www.anchorterminal.com/compare/n8n-vs-windmill.md)
- [n8n API + MCP vs Workato API + MCP](https://www.anchorterminal.com/compare/n8n-vs-workato.md)
- [Paragon ActionKit + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/paragon-vs-power-automate.md)
- [Pipedream API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/pipedream-vs-power-automate.md)
- [Microsoft Power Automate vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-tray.md)
- [Microsoft Power Automate vs Windmill API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-windmill.md)
- [Microsoft Power Automate vs Workato API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-workato.md)