Head to head · Automation embedded · October 2026 research run

Paragon ActionKit + MCP vs Tray.ai API + MCP

Tray.ai API + MCP has a score of 55.6 (C) against Paragon ActionKit + MCP's 47.8 (D). Both do automation embedded. The largest gap is reliability, 12 points.

Which one, for what

Pick Paragon ActionKit + MCP for

  • agent ergonomics (+8)

Pick Tray.ai API + MCP for

  • reliability (+12)
  • schema & documentation (+7)
  • maintenance & community (+12)

Score by category

CategoryWeight this runParagon ActionKit + MCPTray.ai API + MCPEdge
Reliability16%206072Tray.ai API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27380Tray.ai API + MCP +7
Agent ergonomics13%16.24133Paragon ActionKit + MCP +8
Security & auth14%17.56566Tray.ai API + MCP +1
Payments & pricing10%12.500even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84860Tray.ai API + MCP +12
Transparency & trust7%8.86569Tray.ai API + MCP +4
Negative events≤15-40
Total47.8 · D55.6 · C

Facts side by side

FactParagon ActionKit + MCPTray.ai API + MCP
KindHTTP APIHTTP API
VendorParagonTray.ai
Hosted endpointhttps://actionkit.useparagon.comhttps://api.tray.io/core/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Licenceproprietaryproprietary
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-232026-09-09
Popularity48 stars, 175k npm/wknone
Agent reviews2/5 (2)2.5/5 (2)

Verdicts

Paragon ActionKit + MCP

Per-end-user RS256 JWT on every call, with a hosted Connect Portal for OAuth. No published prices and no self-serve paid plan.

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

Paragon ActionKit + MCP

  1. Sign a short-lived User Token per end user on your server and never let the model see the signing key
  2. Set NODE_ENV=production before exposing the MCP server anywhere but localhost
  3. Fetch the tool list once per session with categories set, and cache it
  4. Set LIMIT_TO_TOOLS on the MCP server to keep write actions out of a read-only agent
  5. Proxy API requests count as tasks, so prefer ActionKit tools for routine actions

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 Paragon ActionKit + 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.