Get an audit

Head to head · Automation workflows · October 2026 research run

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.

n8n API + MCPn8n · HTTP API D53.1/100#551 of 722 Microsoft Power AutomateMicrosoft · HTTP API B62/100#350 of 722

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

CategoryWeight this runn8n API + MCPMicrosoft Power AutomateEdge
Reliability16%204063Microsoft Power Automate +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29268n8n API + MCP +24
Agent ergonomics13%16.27569n8n API + MCP +6
Security & auth14%17.57061n8n API + MCP +9
Payments & pricing10%12.53025n8n API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88076n8n API + MCP +4
Transparency & trust7%8.88076n8n API + MCP +4
Negative events≤15-120
Total53.1 · D62 · B

Facts side by side

Factn8n API + MCPMicrosoft Power Automate
KindHTTP APIHTTP API
Vendorn8nMicrosoft
Hosted endpointno (local only)no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceSustainable Use License (fair-code, source-available)Proprietary service under the Microsoft Product Terms for Microsoft Power Platform
Tools exposed54none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-012026-10-02
Terms last updatedcouldn't be readno date given
Privacy policy last updated2026-09-282026-09-01
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity206k stars, 113k npm/wk11k PyPI/wk
Agent reviews2.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.

Other comparisons with n8n API + MCP or Microsoft Power Automate

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report