Head to head · Human approval · October 2026 research run

Permit MCP Gateway vs Temporal

Temporal scores 76.6 (BB) on agent readiness against Permit MCP Gateway's 57.3 (C), and leads in 6 of 7 scored categories. Both do human approval.

Best human approval and handoff for AI agents · All 66 human approval comparisons

Best auth and delegated access for AI agents · All 168 agent auth comparisons

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

Permit MCP Gateway C

Best for A security team that wants approvals and per-user limits on MCP tools across many clients without touching agent code.

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Temporal loses 3 points for them

Watch for

Approvals and on-premises deployment are Enterprise only, priced on request

Temporal BB

Best for A team that already runs, or wants to run, agents as durable workflows with strict guarantees and an audit trail per run.

Ahead on

  • Reliability, 80 against 55
  • Schema & documentation, 91 against 53
  • Security & auth, 88 against 80
  • Maintenance & community, 90 against 28
  • Transparency & trust, 91 against 46

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source
  • Rated higher by the reviewer agents, 3.6 against 2.5 out of 5

Watch for

No reviewer inbox, notifications or routing, so the human side is all your code

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Temporal +62

Permit MCP Gateway 28

No release notes or changelog for the gateway, and the docs changelog page still says the Canny changelog has no entries after 16 May 2024. The newest gateway capability recorded in the docs repository is the HTTP egress proxy, added on 28 July and extended on 30 July 2026, 97 days before this check (10). The gateway docs changed on 17 and 20 September and 6 October 2026 with rewrites and new answer blocks. Docs commits are not releases or changelog entries, and the release dates of the @permitio/agent-security-cli package could not be read, so no dated release falls in the 90 days from 6 August (0). Closed service with a Slack community and support email (5 of 15). Permit SDKs in six languages for the policy API, none needed for the gateway (10 of 15). The docs repository's only GitHub workflow, an Algolia crawl, was removed on 17 September; a Dependabot config and a Netlify build with link checks remain, and the line keeps its earlier partial value (3 of 10).

Temporal 90

Python SDK temporalio 1.35.0 on 28 October and TypeScript 1.25.0 on 27 October, after server patch releases v1.32.1 on 7 October and v1.31.4 and v1.30.8 on 9 October, which carry the fixes for the 12 October server CVEs. v1.33.0 is still unreleased, with a v1.33.0-166.0 release-candidate tag on 28 October (30). Python 1.32.0 to 1.35.0, TypeScript 1.22.0 to 1.25.0 and the server patches all fall in the 90 days from 3 August (20). We couldn't sample issue reply times, since GitHub's pages answered 403 on 6 and 17 October and 1 November (15 of 25). Current official SDKs in eight languages (15). CI with Codecov and flaky-test reports on the server repository, per the 1 October check, not re-read on 1 November (10). 30 + 20 + 15 + 15 + 10 = 90.

Transparency & trust Temporal +45

Permit MCP Gateway 46

Closed service under terms whose revision list ends on 1 July 2026 (termination and amendment provisions), naming Permit Inc., a Delaware corporation, under Delaware law (15 of 30). The docs say hosted traffic, including tool arguments and upstream responses, passes through Permit's infrastructure, and that customer-controlled or on-premises deployments keep it in your network. The terms let Permit delete data on termination, the trust centre says retention is limited by purpose, contract and legal requirements, and gateway audit logs are kept 7 days on Community (15 of 30). The terms let Permit change the service without notice, and the changelog stopped in May 2024 (0 of 20). The trust centre now lists nine subprocessors with their purposes (AWS, Datadog, Google, Twilio Segment, Mixpanel, Stripe, Sentry, Auth0, WorkOS) and promises at least 14 days' notice of changes, and says hosted services run on AWS, with no locations per provider (15 of 20).

Temporal 91

Server and SDKs under MIT (30). The privacy policy (updated 22 April 2026, re-read 1 November) gives retention periods for personal data, Cloud keeps closed workflow histories 30 days by default (1 to 90), and client-side encryption keeps payloads unreadable to Temporal. The DPA at temporal.io/dpa (effective 10 October 2024), per the 6 October check, has Temporal destroy customer personal data on request, gives 15 days to object to a new subprocessor and uses the Standard Contractual Clauses with the UK Addendum. These agree (30). Dated deprecation notices, such as the audit log request_id field, still marked for removal on or after 1 November 2026 when read on 1 November, and published release stages (15 of 20). The trust centre lists seven subprocessors with purpose and location of processing (Auth0, AWS, Elastic, Google Cloud, IBM, Microsoft Azure, WorkOS), last updated 29 May 2026, re-read 1 November (20). 30 + 30 + 15 + 20 = 95.

Schema & documentation Temporal +38

Permit MCP Gateway 53

The gateway adds no tools of its own and passes upstream tool schemas through. Permit's management API has an OpenAPI-backed reference (15 of 25). No llms.txt or Markdown copies of the docs found (0). The docs say what the agent sees while waiting, what a rejection returns and what the gateway doesn't cover (15 of 20). Approval rules are toggles and trust levels in the dashboard, with nothing for the agent to type (8 of 15). The waiting message, the rejection error and the 429 body are documented with examples (12 of 15). The product changelog on Canny has no entry after May 2024, and the gateway has no changelog (3 of 15).

Temporal 91

OpenAPI v3 (and v2) documents for the HTTP API in the temporalio/api repository, on top of the protobuf definitions, still served on 1 November, with temporalio/api tagged to v1.64.0 (25). llms.txt and llms-full.txt for the docs, and every page as Markdown (10). The approval pattern page says when to wait on a Signal and the docs say when an Update fits better because the sender needs an answer, per the 6 October check (15 of 20). Protobuf-typed API and typed Signal payloads in each SDK (13 of 15). Approval examples in Python, TypeScript, Java and Go, and the gRPC errors that count against the SLA are listed (13 of 15). GitHub releases, SDK release notes and dated deprecation notices (15). 25 + 10 + 15 + 13 + 13 + 15 = 91.

Reliability Temporal +25

Permit MCP Gateway 55

Permit's status page at permit-io.instatus.com lists Backend, OPAL, Frontend, Marketing Website, PDP Deltas and PDP Data, all US East, with no component for the gateway or agent.security. A vendor page with no component for the product takes 15 (15). The incident line is read from the components the gateway depends on. The architecture page says the hosted gateway calls the Cloud PDP on every tool call and that gateway policies update through OPAL. history.atom shows three OPAL US East outages since 6 August, on 27 October (29 minutes), 1 November (9 minutes) and 4 November (15 minutes), each one component for under an hour, so minor (20). The hosted gateway rate-limits per client IP on sign-in, client registration and MCP endpoints, and the docs say they don't publish the numbers (0). A 429 carries a rate_limited JSON body and the docs say to back off and grow the wait on each retry, with no safe-retry guidance for tool calls that write, which this run scores 10 (10). The gateway pricing page lists 99.95 per cent uptime on Pro and 99.99 per cent on Enterprise, and Permit's pricing page an optional 99.99 per cent SLA, but no SLA document was found (0). The gateway carries no beta label, and approvals carry an Enterprise label (10).

Temporal 80

Status page at status.temporal.io (Atlassian Statuspage) with components for 14 AWS regions, 6 GCP regions and 8 global services (20). On 1 November its RSS history feed was read (its robots.txt disallows the /api/ feed used on 6 October). In the 90 days from 3 August one major sits on the core path. A configuration change on 10 September left some namespaces in us-central1 and asia-southeast2 with errors and blocked workflow progress from at least 20:51 until mitigation at 21:55 UTC, with residual issues cleared by 07:21 the next day. Statuspage marked a control plane, Cloud Ops API and UI incident on 5 October (20:23 to 20:52 UTC) critical, which isn't workflow execution. The 31 July to 1 August Usage API and UI outage has left the window. Since 17 October there are only minor entries. A retrospective notice on 19 October says some clients of GCP namespaces saw intermittent TCP connection resets between 6 and 15 October, limited by SDK retries, and on 31 October some GCP us-east4 namespaces saw intermittent request failures from 13:31 until a fix at 13:48, resolved 14:16 UTC. Earlier minor entries include 9 October in us-east-1 (22:33, recovered by 23:11 after failover) and 14 October in us-west1 (12:21:15 to 12:22:00). New namespace creation in GCP us-central1, us-east4 and europe-west3 is restricted for capacity, with existing namespaces unaffected. One major outage, so 10 of 30. Limits published with numbers, 500 Actions a second per namespace by default and 30 Visibility API calls a second, re-read on 1 November, with 10 schedule requests a second per the 17 October check (15). Throttled calls return ResourceExhausted, which SDK clients retry under the default gRPC retry policy, and signals, starts and updates are throttled last. Workflow IDs and request IDs make starts and signals safe to retry (15). Contractual SLA at temporal.io/sla of 99.9 per cent for a standard single-region namespace and 99.99 per cent with same-region replication, multi-region or multi-cloud, with service credits, re-read on 1 November (10). Signals, timers and Updates are GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.

Security & auth Temporal +8

Permit MCP Gateway 80

OAuth 2.1 authorisation server per host with dynamic client registration, consent and a trust ceiling, admin revocation and sessions that end 90 days after the last tool call (30). Trust levels per tool, a maximum per user set by the admin, approval rules per tool, server or level, and a timeout that always rejects (20). The docs state prompt injection is out of scope and should be handled in the client and model, and the gateway doesn't inspect what tools return (5 of 15). Every tool call goes to Permit audit logs, and approval history records the outcome, the deciding admin and the time taken. Audit log retention isn't published (13 of 15). The trust centre states a SOC 2 Type II renewal in January 2026 with sections 1 and 2 public and the full report on request, HIPAA BAAs and annual penetration tests, and routes security concerns to help@permit.io with no acknowledgement time. No disclosure policy was found, security.txt answers a not-found page, and osv.dev lists no advisories for Permit packages (12 of 20).

Temporal 88

Namespace-scoped API keys tied to users or service accounts, with RBAC, expiry, emails at 30, 20 and 10 days before expiry and rotation guidance, or mTLS per namespace, per the 1 October check, not re-read on 1 November (30). Read-only account role and namespace-scoped service accounts (18 of 20). It returns your own workflow data and the signal payloads you send (10). Control-plane audit logs export to Kinesis or Pub/Sub, data-plane events such as Workflow Start and Terminate are left out, and each workflow's event history records every signal (13 of 15). temporal.io/.well-known/security.txt is valid (security@temporal.io, expires 15 January 2027, re-read 1 November) and points to a responsible disclosure policy with safe harbour. Temporal is a CVE Numbering Authority and announces CVEs on its trust centre with fixed versions, most recently CVE-2026-104355 (High) and CVE-2026-89140 (Medium) in Temporal Server on 12 October and CVE-2026-108126 (Medium) in temporal-proxy on 15 October, and on 22 and 27 October it posted notices that Cloud and Server weren't affected by outside CVEs. SOC 2 Type II, HIPAA and GDPR, and penetration testing by outside partners. No bug bounty found (17 of 20). 30 + 18 + 10 + 13 + 17 = 88.

Score by category

CategoryWeightPermit MCP GatewayTemporalEdge
Reliability16%5580Temporal +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5391Temporal +38
Agent ergonomics13%8385Temporal +2
Security & auth14%8088Temporal +8
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2890Temporal +62
Transparency & trust7%4691Temporal +45
Negative events≤150-3
TotalC 57.3/100BB 76.6/100

Facts side by side

FactPermit MCP GatewayTemporal
KindPlatformPlatform
VendorPermit.ioTemporal Technologies
Hosted endpointhttps://{subdomain}.agent.security/mcpno (local only)
TransportsStreamable HTTPHTTP
AuthOAuthOAuth or key
PricingPaidPay per use
x402nono
LicencenoneMIT
Read-only variant documentednoyes
llms.txtnoyes
Last releasenone2026-10-28
Terms last updatedno date given2024-10-01
Privacy policy last updated2024-07-292026-04-22
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)3.6/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Temporal higher.

ReviewerPermit MCP GatewayTemporal
KeelOperations and maintenance reviewer 1/5 Terms allow change without notice 4/5 Older lines patched, removals dated
WardenSecurity auditor 4/5 Timeouts reject and disconnects cancel 4/5 A read-only role, and the sender is the gate

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Permit MCP Gateway

No SDK or client change, since the client points at the gateway URL and keeps its tool list, and each tool call is checked against Permit policy and logged. Approvals and on-premises deployment are Enterprise only, rate limits are unpublished, and the status page has no gateway component.

Temporal

Waits of any length with a timeout survive worker restarts and deploys. No reviewer inbox, notifications or routing, so the human side is all your code.

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

Temporal

  1. Put the decision in a typed Signal payload (approver, decision, comments, timestamp) instead of a bare boolean
  2. Always wait with a timeout and treat the timeout path as a rejection or an escalation on purpose
  3. Create new Cloud namespaces in an AWS region or an open GCP region; GCP us-central1, us-east4 and europe-west3 need a support exception
  4. Use an Update instead of a Signal when the approver's tool needs an acknowledgement back
  5. Expect ResourceExhausted under load and let the SDK retry it, since signals are throttled last
  6. Read the SDK changelog's Breaking Changes section before a minor upgrade; 1.35.0 changes the schedule catch-up default and rejects async update validators

Questions

Which is better for AI agents, Permit MCP Gateway or Temporal?

Temporal scores 76.6 (BB) on agent readiness against Permit MCP Gateway's 57.3 (C), and leads in 6 of 7 scored categories.

Are Permit MCP Gateway and Temporal open source?

No open-source release is listed for Permit MCP Gateway. Temporal is open source (MIT).

Other comparisons with Permit MCP Gateway or Temporal

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.