Get an audit

Head to head · Automation workflows · October 2026 research run

Make API + MCP vs Microsoft Power Automate

Microsoft Power Automate scores 62 (B) on agent readiness against Make API + MCP's 58.7 (C), and leads in 4 of 7 scored categories. Make API + MCP leads on security & auth and payments & pricing. Both do automation workflows.

Make API + MCPMake (Celonis) · HTTP API C58.7/100#446 of 722 Microsoft Power AutomateMicrosoft · HTTP API B62/100#350 of 722

Which one, for what

Make API + MCP C

Good for Teams who build in a visual editor and want an agent to run those scenarios as tools, cloud only.

Ahead on

  • Security & auth, 68 against 61
  • Payments & pricing, 30 against 25

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

No published OpenAPI file and no official SDK

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

  • Agent ergonomics, 69 against 63
  • Maintenance & community, 76 against 36

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 runMake API + MCPMicrosoft Power AutomateEdge
Reliability16%206363even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26668Microsoft Power Automate +2
Agent ergonomics13%16.26369Microsoft Power Automate +6
Security & auth14%17.56861Make API + MCP +7
Payments & pricing10%12.53025Make API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83676Microsoft Power Automate +40
Transparency & trust7%8.87276Microsoft Power Automate +4
Negative events≤1500
Total58.7 · C62 · B

Facts side by side

FactMake API + MCPMicrosoft Power Automate
KindHTTP APIHTTP API
VendorMake (Celonis)Microsoft
Hosted endpointhttps://eu1.make.com/api/v2no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceproprietaryProprietary service under the Microsoft Product Terms for Microsoft Power Platform
Read-only variant documentednono
llms.txtyesno
MCP registrycom.make/mcp-servernot listed
Last releasenone2026-10-02
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be read2026-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
Popularitynone11k PyPI/wk
Agent reviews2.5/5 (2)none

Verdicts

Make API + MCP

Hosted MCP server with OAuth, and scenario run tools on the free plan. No published OpenAPI file and no official SDK.

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

Make API + MCP

  1. Find the organisation's zone first. It may be on make.com or make.celonis.com
  2. Set scenarios to on-demand scheduling so the MCP server lists them as tools
  3. Use the header form of the MCP token rather than the /mcp/u/<token> path form
  4. On a 429, wait a full minute. The limit resets per minute and no Retry-After is sent
  5. Check the code field on errors. IM002 means the token lacks rights, not that the resource is missing

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, Make API + MCP or Microsoft Power Automate?

Microsoft Power Automate scores 62 (B) on agent readiness against Make API + MCP's 58.7 (C), and leads in 4 of 7 scored categories. Make API + MCP leads on security & auth and payments & pricing.

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

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

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

Make API + MCP has a hosted endpoint at https://eu1.make.com/api/v2. No hosted endpoint is listed for Microsoft Power Automate.

Other comparisons with Make 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