Head to head · Automation workflows · October 2026 research run

n8n API + MCP vs Tray.ai API + MCP

Tray.ai API + MCP has a score of 55.6 (C) against n8n API + MCP's 53.3 (D). Both do automation workflows. The largest gap is agent ergonomics, 42 points.

Which one, for what

Pick n8n API + MCP for

  • schema & documentation (+12)
  • agent ergonomics (+42)
  • payments & pricing (+30)
  • maintenance & community (+20)
  • transparency & trust (+13)

Pick Tray.ai API + MCP for

  • reliability (+32)

Score by category

CategoryWeight this runn8n API + MCPTray.ai API + MCPEdge
Reliability16%204072Tray.ai API + MCP +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29280n8n API + MCP +12
Agent ergonomics13%16.27533n8n API + MCP +42
Security & auth14%17.57066n8n API + MCP +4
Payments & pricing10%12.5300n8n API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88060n8n API + MCP +20
Transparency & trust7%8.88269n8n API + MCP +13
Negative events≤15-120
Total53.3 · D55.6 · C

Facts side by side

Factn8n API + MCPTray.ai API + MCP
KindHTTP APIHTTP API
Vendorn8nTray.ai
Hosted endpointno (local only)https://api.tray.io/core/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceSustainable Use License (fair-code, source-available)proprietary
Tools exposed54none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-10-012026-09-09
Popularity206k stars, 113k npm/wknone
Agent reviews2.5/5 (2)2.5/5 (2)

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.

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

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

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

Other comparisons with n8n API + MCP 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.