Head to head · Human approval · October 2026 research run

Orkes Conductor Human tasks vs Permit MCP Gateway

Permit MCP Gateway scores 57.3 (C) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 3 of 7 scored categories. Orkes Conductor Human tasks leads on schema & documentation and maintenance & community. Both do human approval.

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

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

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

Which one, for what

Orkes Conductor Human tasks C

Best for Teams that already orchestrate agents as Conductor workflows and need formal routing, per-assignee deadlines and escalation without writing them.

Ahead on

  • Schema & documentation, 65 against 53
  • Maintenance & community, 81 against 28

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow

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.

Ahead on

  • Reliability, 55 against 32
  • Agent ergonomics, 83 against 69

Watch for

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

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 Orkes Conductor Human tasks +53

Orkes Conductor Human tasks 81

Conductor OSS v3.33.0 tagged on 2026-10-23, with a v3.34.0 release candidate on 2026-10-29 that doesn't count (30). Seven releases in the 90 days from 6 August, v3.32.0 (7 August), v3.32.1 (12 August), v3.32.2 (3 September), v3.32.3 (9 September), v3.32.4 (10 September), v3.32.5 (24 September) and v3.33.0 (20). The MCP server has no commit since 2026-01-08, and GitHub's issue pages couldn't be read on 4 November, so responsiveness stays per the 1 October check (12 of 25). Official SDKs are current, conductor-python v2.0.0 (30 July 2026) and conductor-javascript v4.0.0 (29 July 2026), with Go, Java and C# per the 1 October check (15). CI runs the tests on the server and both SDK repositories, with results unreadable, and the MCP server's server.json still says 0.1.7 against 0.1.9 in pyproject.toml (4 of 10). 30 + 20 + 12 + 15 + 4 = 81.

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

Reliability Permit MCP Gateway +23

Orkes Conductor Human tasks 32

No public status page found for Orkes Cloud or the Developer Edition, in a web search or the docs repository on 4 November (0), so no readable incident history (5). API rate limits aren't published. The rate-limit page covers per-task execution limits you set yourself, and the Developer Edition says its limits may change (0). No 429 or backoff guidance found, but workflow starts take an idempotency key with FAIL, RETURN_EXISTING or FAIL_ON_RUNNING strategies (7 of 15, a partial kept under the in-between rule). The Cloud support policy sets 99.9 or 99.0 per cent by plan with service credits, and Enterprise goes up to 99.99 per cent (10). The Human task is GA (10). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. 0 + 5 + 0 + 7 + 10 + 10 = 32.

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

Agent ergonomics Permit MCP Gateway +14

Orkes Conductor Human tasks 69

The MCP server has 19 tools and no read-only subset (15), and the Human task search pages with start and size and filters (20). Averaged to 17 of 25. Search by state, assignee, claimant, full text and task input or output queries (20). Few documented API error responses (10 of 20). Idempotency keys with three strategies on workflow start, no MCP annotations (12 of 20). Official SDKs in Java, Python, JavaScript, Go and C#, but a first approval needs a form, a workflow, a Human task and an application key (10 of 15). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means.

Permit MCP Gateway 83

It adds nothing to the agent's context, since the client keeps the upstream tool list (25). The approval queue has batch actions for the admin, but nothing pages or filters for the agent (10 of 20). The agent gets a waiting message with the timeout and a rejection error carrying the admin's reason, which it can act on (18 of 20). Each tool gets a low, medium or high trust level at import, close to read-only and destructive hints, and a dropped connection cancels the request instead of leaving it to run later (15 of 20). One URL change and no SDK, with Permit SDKs in six languages for the policy side (15).

Schema & documentation Orkes Conductor Human tasks +12

Orkes Conductor Human tasks 65

No public OpenAPI found for the Orkes API. The 19 MCP tools are typed through FastMCP but none covers Human tasks (10 of 25). llms.txt exists but is the whole documentation in one 2.57 MB file with no index, which an agent can't use as a map, so 7 of 10. Each Human task endpoint has its own reference page with purpose and parameters, and the operator page explains assignment, expiry and completion strategies (14 of 20). Parameters are typed in tables with enums for states and strategies, and forms carry their own schema (12 of 15). curl and SDK examples, a workflow error-handling guide, few documented API error responses (10 of 15). Conductor OSS releases on GitHub and a product changelog page (12 of 15). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. The docs repository's static/llms.txt is 2,000,447 bytes today, last changed on 2026-07-20, still one file with no index.

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

Score by category

CategoryWeightOrkes Conductor Human tasksPermit MCP GatewayEdge
Reliability16%3255Permit MCP Gateway +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6553Orkes Conductor Human tasks +12
Agent ergonomics13%6983Permit MCP Gateway +14
Security & auth14%7780Permit MCP Gateway +3
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8128Orkes Conductor Human tasks +53
Transparency & trust7%4646even
Negative events≤15-10
TotalC 55.5/100C 57.3/100

Facts side by side

FactOrkes Conductor Human tasksPermit MCP Gateway
KindPlatformPlatform
VendorOrkesPermit.io
Hosted endpointhttps://developer.orkescloud.com/apihttps://{subdomain}.agent.security/mcp
TransportsHTTP, stdioStreamable HTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicenceApache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)none
Tools exposed19none
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.conductor-oss/conductor-mcpnot listed
Last release2026-10-23none
Terms last updatedno date givenno date given
Privacy policy last updated2022-02-232024-07-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

ReviewerOrkes Conductor Human tasksPermit MCP Gateway
KeelOperations and maintenance reviewer 2/5 The engine ships, the MCP server stopped in January 1/5 Terms allow change without notice
WardenSecurity auditor 3/5 Fails closed if asked, tokens can live forever 4/5 Timeouts reject and disconnects cancel

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

Orkes Conductor Human tasks

Escalation chains with a time limit per assignee and a choice of leaving the task open or failing the workflow. No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow.

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.

Before you call either

Orkes Conductor Human tasks

  1. Give every assignment you want to escalate from a non-zero slaMinutes, since 0 never expires and nothing can follow it
  2. Pick TERMINATE for risky actions so an unanswered approval fails the workflow instead of staying open to anyone
  3. Start approval workflows with an idempotencyKey and RETURN_EXISTING, so a retried start doesn't ask twice
  4. Refresh the JWT from /api/token with a set expiry instead of requesting one that never expires
  5. Fetch single doc pages, not llms.txt, which is the whole documentation in 2.57 MB
  6. Run Conductor OSS v3.30.2 or later if you self-host, since earlier 3.2x versions carry CVE-2026-58138

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

Questions

Which is better for AI agents, Orkes Conductor Human tasks or Permit MCP Gateway?

Permit MCP Gateway scores 57.3 (C) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 3 of 7 scored categories. Orkes Conductor Human tasks leads on schema & documentation and maintenance & community.

Are Orkes Conductor Human tasks and Permit MCP Gateway open source?

Orkes Conductor Human tasks is open source (Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)). No open-source release is listed for Permit MCP Gateway.

Other comparisons with Orkes Conductor Human tasks or Permit MCP Gateway

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.