Get an audit

Head to head · Automation workflows · October 2026 research run

Microsoft Power Automate vs Tray.ai API + MCP

Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema & documentation and security & auth. Both do automation workflows.

Microsoft Power AutomateMicrosoft · HTTP API B62/100#350 of 722 Tray.ai API + MCPTray.ai · HTTP API C55.5/100#508 of 722

Which one, for what

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 33
  • Payments & pricing, 25 against 0
  • Maintenance & community, 76 against 60
  • Transparency & trust, 76 against 68

Watch for

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

Tray.ai API + MCP C

Good for SaaS vendors embedding integrations for their customers, with an agent that acts per end user.

Ahead on

  • Reliability, 72 against 63
  • Schema & documentation, 80 against 68
  • Security & auth, 66 against 61

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No published prices and no self-serve plan

Score by category

CategoryWeight this runMicrosoft Power AutomateTray.ai API + MCPEdge
Reliability16%206372Tray.ai API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26880Tray.ai API + MCP +12
Agent ergonomics13%16.26933Microsoft Power Automate +36
Security & auth14%17.56166Tray.ai API + MCP +5
Payments & pricing10%12.5250Microsoft Power Automate +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87660Microsoft Power Automate +16
Transparency & trust7%8.87668Microsoft Power Automate +8
Negative events≤1500
Total62 · B55.5 · C

Facts side by side

FactMicrosoft Power AutomateTray.ai API + MCP
KindHTTP APIHTTP API
VendorMicrosoftTray.ai
Hosted endpointno (local only)https://api.tray.io/core/v1
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceProprietary service under the Microsoft Product Terms for Microsoft Power Platformproprietary
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-022026-09-09
Terms last updatedno date given2025-01-28
Privacy policy last updated2026-09-012026-01-01
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity11k PyPI/wknone
Agent reviewsnone2.5/5 (2)

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 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.

Tray.ai API + MCP

Call any connector operation directly with a per-end-user token, no workflow needed. No published prices and no self-serve plan.

Before you call either

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/

Tray.ai API + MCP

  1. Use a user token when acting for a customer and the master token only for admin work
  2. Parse the body of call-connector responses for upstream status codes before treating a 200 as success
  3. Point Headless MCP at the workspace's region, api.eu1.tray.io or api.ap1.tray.io outside the US
  4. Pick the workspace at OAuth sign-in. Headless MCP binds it to the session and takes no workspace ID
  5. Ask before any Headless MCP delete. The server won't

Questions

Which is better for AI agents, Microsoft Power Automate or Tray.ai API + MCP?

Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema & documentation and security & auth.

Do Microsoft Power Automate and Tray.ai API + MCP need an API key?

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

Can an agent call Microsoft Power Automate and Tray.ai API + MCP without installing anything?

No hosted endpoint is listed for Microsoft Power Automate. Tray.ai API + MCP has a hosted endpoint at https://api.tray.io/core/v1.

Other comparisons with Microsoft Power Automate or Tray.ai API + MCP

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