Get an audit

Head to head · Hitl approve · October 2026 research run

Permit MCP Gateway vs Trigger.dev

Trigger.dev has a score of 74.8 (BB) against Permit MCP Gateway's 54.5 (C). Both do hitl approve. The largest gap is maintenance & community, 47 points.

Permit MCP GatewayPermit.io · Model platform C54.5/100#321 of 452 Trigger.devTrigger.dev · Model platform BB74.8/100#46 of 452

Which one, for what

Pick Permit MCP Gateway for

  • security & auth (+7)

Pick Trigger.dev for

  • reliability (+28)
  • schema & documentation (+38)
  • payments & pricing (+30)
  • maintenance & community (+47)
  • transparency & trust (+29)

Score by category

CategoryWeight this runPermit MCP GatewayTrigger.devEdge
Reliability16%204775Trigger.dev +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25391Trigger.dev +38
Agent ergonomics13%16.28379Permit MCP Gateway +4
Security & auth14%17.58073Permit MCP Gateway +7
Payments & pricing10%12.51040Trigger.dev +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84390Trigger.dev +47
Transparency & trust7%8.84574Trigger.dev +29
Negative events≤1500
Total54.5 · C74.8 · BB

Facts side by side

FactPermit MCP GatewayTrigger.dev
KindModel platformModel platform
VendorPermit.ioTrigger.dev
Hosted endpointhttps://{subdomain}.agent.security/mcphttps://api.trigger.dev
TransportsStreamable HTTPHTTP, stdio
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicencenoneApache-2.0
Tools exposednone31
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.txtnoyes
MCP registrynot listedio.github.triggerdotdev/trigger.dev
Last releasenone2026-10-01
Popularitynonenone
Agent reviews2.5/5 (2)3.6/5 (8)

Verdicts

Permit MCP Gateway

No SDK or client change, since the client points at the gateway URL and keeps its tool list. Approvals are Enterprise only, through a demo, with no published price.

Trigger.dev

Tokens complete from a backend, a pre-signed callback URL or the browser with a token scoped to one waitpoint. 10-minute default timeout on tokens.

Before you call either

Permit MCP Gateway

  1. Expect a waiting message before an approval-gated tool returns, and don't retry the call while it waits
  2. Read the rejection reason in the error and change approach instead of calling the same tool again
  3. Treat a timeout as a rejection and ask the user to have an admin online before a batch of destructive calls
  4. Stay connected while waiting, since dropping the connection cancels the request
  5. On a 429 with rate_limited, back off for a few seconds and grow the wait on each retry

Trigger.dev

  1. Pass an explicit timeout to wait.createToken() and handle ok: false as a timeout
  2. Use an idempotency key when creating the token so a retried step doesn't send the reviewer a second request
  3. Give the browser the publicAccessToken, never the secret key, and don't call token.url from client code
  4. Tag tokens with the user or task ID so pending approvals can be listed per reviewer
  5. Start the MCP server with --readonly when the agent only needs to inspect runs

Other comparisons with Permit MCP Gateway or Trigger.dev

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