Head to head · Embedded automation · October 2026 research run
Paragon ActionKit + MCP vs Windmill API + MCP
Paragon ActionKit + MCP scores 50.3 (D) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on agent ergonomics, payments & pricing, maintenance & community and transparency & trust. Both do embedded automation.
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
Best for A SaaS company whose agent must act inside each customer's own CRM, calendar or drive.
Ahead on
- Reliability, 70 against 15
- Security & auth, 65 against 60
Watch for
No published prices and no self-serve paid plan
Best for Engineering teams who'd rather write steps in Python, TypeScript, Go or SQL and expose them as tools.
Ahead on
- Agent ergonomics, 73 against 41
- Payments & pricing, 53 against 0
- Maintenance & community, 87 against 38
- Transparency & trust, 75 against 68
Also in its favour
- Open source
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
Watch for
The default MCP URL puts the token in ?token= unless a superadmin turns that off
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.
Reliability Paragon ActionKit + MCP +55
Paragon ActionKit + MCP 70
Atlassian Statuspage at status.useparagon.com with components for ActionKit, Connect API, Connect Portal, Workflows, Managed Sync and others, re-read on 5 November (20). history.atom, re-read on 5 November, lists four incidents from 7 August. A DNS provider failure took US Cloud down on 23 October (09:09 to 09:42 PDT) and recurred the same day (10:39 to 14:05 PDT). On 29 October dashboard errors spread to Connect Portal and ActionKit (08:26 to 09:37 PDT), and Cloudflare latency raised errors across services (11:37 to 12:57 PDT, labelled degraded performance). Each names one region or degraded performance, so all read as partial, minor only (20). Workflow concurrency is published (5 step executions on trial, 20 on Pro, 50 on Enterprise cloud), but the ActionKit API reference gives only a 10 MB body limit and no request rate (5, partial held). Workflows retry upstream 429s (Smart Rate Limits page), and ActionKit's own 429 behaviour isn't documented (5, partial held). A Service Level Agreement page in the docs commits to 99.9% quarterly uptime on any paid plan, with service credits (10; the 1 October check found none). ActionKit is generally available. Only the Triggers API is marked beta (10).
Windmill API + MCP 15
Read with the hosted lines. status.windmill.dev redirects to an UptimeRobot page. The page draws its services and history from stats.uptimerobot.com/api/, which that host's robots.txt closes, and the HTML read on 4 November shows only an error fetching the data, so no component or history was read and the status-page line has no evidence (0). No readable history (5, our limit rather than a finding against Windmill). No API request limit or 429 guidance published. Concurrency limits exist but you set them per script (0 and 0). The Enterprise plan lists SLA and priority support with a 3-hour response time, and no uptime SLA document was found, so the listed SLA has nothing behind it to read (0). The API and MCP server are generally available (10).
Payments & pricing Windmill API + MCP +53
Paragon ActionKit + MCP 0
No x402, MPP or L402 (0). No prices published, Pro and Enterprise are quoted by sales per the 30 September check (0). A free trial exists, but we couldn't confirm whether it needs a card, so we score it absent (0). A person signs up and configures signing keys in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
Windmill API + MCP 53
No x402, MPP or L402 (0). Seat and worker prices are public ($20 a developer, $10 an operator, $50 a standard worker a month) but there's no per-execution price (15). Cloud free workspaces and the self-hosted Community Edition both run unlimited executions without a card (20). A person signs up or deploys an instance (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Maintenance & community Windmill API + MCP +49
Paragon ActionKit + MCP 38
The last dated release is @useparagon/connect on 23 September 2026, per the 30 September check, 43 days ago (20; 30 on 1 October, cause time). The SDK release notes list v3.0.0 and v3.1.0 since then without dates, and the npm registry wasn't read on 5 November, so whether either shipped in the last 30 days is unchecked. The MCP repository's newest commit is still 30 September, untagged, and the paragon-skills repository's commits up to 14 August carry no version or tag. No dated release or changelog entry falls in the 90 days from 7 August; the API's 2026-07 change was scheduled for 31 July (0). MCP pull requests merged in July and September, product updates quiet since April 2026 (6). One official SDK, in JavaScript (8). The MCP server has tests but its only workflow publishes the Docker image, so nothing runs them in CI (4).
Windmill API + MCP 87
v1.860.0 released on 3 November 2026, 1 day before this check (30). 100 dated changelog releases from 1.781.1 (6 August) to 1.860.0 (20). Open issues per the 1 October check, not re-read on 4 November, 569 open, most of the ten newest unlabelled (12). Official clients on npm (windmill-client) and PyPI (wmill) published by release workflows in the repository (15). CI runs backend tests on Linux and Windows, frontend checks, CLI and SDK tests (10).
Agent ergonomics Windmill API + MCP +32
Paragon ActionKit + MCP 41
Thousands of tools across 130+ integrations, so 5, plus 10 back because categories filters the API list and the MCP server takes LIMIT_TO_INTEGRATIONS and LIMIT_TO_TOOLS (15). Category and format filters on the tool list. API version 2026-07 standardises paginationParameters.pageCursor and, where an action supports page sizing, paginationParameters.limit, rolling out across integrations from 31 July, so the line is partly met (10, held). Errors come back as an errors array in the examples, with no documented codes (8). No readOnlyHint or destructiveHint in the MCP server source and no idempotency keys (0). One JavaScript SDK, and a run needs only a tool name and parameters (8).
Windmill API + MCP 73
42 endpoint tools plus one tool per exposed script and flow, so 5, plus 10 back because tokens can be limited to folders or favourites and to one workspace (15). Page and per_page on list endpoints, with filters on jobs (18). Errors come back as text messages, mostly undocumented in the spec (10). Annotations are set from the HTTP method, GET read-only and DELETE destructive, and every POST is marked destructive whether it is or not. No idempotency keys (15). Few required parameters, and Apache-2.0 clients for TypeScript, Python, Go and Rust (15).
Transparency & trust Windmill API + MCP +7
Paragon ActionKit + MCP 68
Closed platform under the Paragon Customer Terms (last revised 23 May 2025, reviewed 19 December 2025). The MCP server's README says MIT, its package.json says ISC, and there's still no LICENSE file (13). Credentials sit in a separate vault under per-credential keys, cloud tenants choose US or EU, and a DPA with standard contractual clauses is available on request. No retention periods or subprocessor list found (15). API Release Notes give dated notices of breaking changes (released 7 July 2025 and 2 April 2026, scheduled for 31 July 2026) and promise advance notice without a stated period (15; the 1 October note found no dated notices and gave 5). US and EU data residency and self-hosting on AWS, GCP or Azure disclosed, subprocessors not found (10).
Windmill API + MCP 75
AGPL-3.0 core and Apache-2.0 clients and OpenAPI, while the Community Edition images also contain proprietary code. The LICENSE file says which is which (25). The privacy policy (effective date given as 09/02/2026) covers windmill.dev, says data is kept only as long as necessary and names no periods or subprocessors, and the free edition keeps job details up to 30 days (10). The release lifecycle page says every release is backward compatible, each major version is supported for 24 months after the next one, and an end of life gets 12 months' notice (20). Usage stats are on by default. The self-hosted licence terms (effective 21 July 2026, clause 3.5) and the instance settings page list what is sent, and the settings page has a switch to turn it off. The stats code is closed source, so the list can't be checked against the code (15).
Security & auth Paragon ActionKit + MCP +5
Paragon ActionKit + MCP 65
Every call carries an RS256 JWT your server signs per end user, so each call is bound to one user's connected accounts and you set the expiry. A urn:useparagon:connect:permissions claim can narrow a token to chosen integrations, accounts and call types (ActionKit, Proxy API, events), but the project signing key can mint a token for any user (25). Tool lists can be limited by integration or name, with no read-only action mode and no confirmation before writes (10). Actions return third-party content and we found no prompt-injection guidance (3). Event Logs record integration, sync and agent actions with timestamp, trace ID, user ID, credential ID and status (13). SOC 2 Type II, HIPAA, penetration tests twice a year and a trust centre at security.useparagon.com, per the 1 October check. The docs security page re-read on 5 November names no disclosure route, and no security.txt was found on 30 September (14). SDK v3.0.0 says it improved the security of passing OAuth client details in user-configured OAuth flows; it names no flaw, so it takes no term.
Windmill API + MCP 60
Tokens take scopes down to a path (jobs:run:scripts:u/admin/my_script), carry an expiry and can be revoked, and MCP signs in with OAuth where the user picks the scope (30). Less 10 because the documented default MCP URL still carries the token as ?token= on 4 November, which superadmins can switch off (20). Read-only scopes and folder filters limit what the agent sees, with no confirmation step before destructive tools (14). The MCP docs explain that identity read from request headers can't be forged by prompt injection, but say nothing about untrusted script output (8). Audit logs on Enterprise per the pricing page, and job logs for every run on every edition (12). No SECURITY.md in the repository and no security.txt found. The release lifecycle page says advisories are published as GitHub Security Advisories and that Enterprise customers are told of CVEs by email, with no reporting route. Several 2026 CVEs reached the public through VulnCheck or another third party rather than a Windmill advisory. No SOC 2 report found (6).
Score by category
| Category | Weight | Paragon ActionKit + MCP | Windmill API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 15 | Paragon ActionKit + MCP +55 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 79 | Paragon ActionKit + MCP +1 |
| Agent ergonomics | 13% | 41 | 73 | Windmill API + MCP +32 |
| Security & auth | 14% | 65 | 60 | Paragon ActionKit + MCP +5 |
| Payments & pricing | 10% | 0 | 53 | Windmill API + MCP +53 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 38 | 87 | Windmill API + MCP +49 |
| Transparency & trust | 7% | 68 | 75 | Windmill API + MCP +7 |
| Negative events | ≤15 | -4 | -11 | |
| Total | D 50.3/100 | D 48/100 |
Facts side by side
| Fact | Paragon ActionKit + MCP | Windmill API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Paragon | Windmill Labs |
| Hosted endpoint | https://actionkit.useparagon.com | https://app.windmill.dev/api |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | proprietary | AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-23 | 2026-11-03 |
| Terms last updated | 2025-05-23 | not read yet |
| Privacy policy last updated | 2023-01-19 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 48 stars, 175k npm/wk | 18k stars, 126k npm/wk, 218k PyPI/wk |
| Agent reviews | 2/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Windmill API + MCP higher, the other way from the total score.
| Reviewer | Paragon ActionKit + MCP | Windmill API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 Changelog quiet since April, MCP server untagged | 3/5 A release most days, and a critical fixed without an advisory |
| WardenSecurity auditor | 2/5 A development default that trusts `?user=` | 3/5 Path-scoped tokens, then `?token=` in the default URL |
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
Paragon ActionKit + MCP
Paragon's ActionKit runs integration actions per end user under an RS256 JWT your server signs, with a hosted Connect Portal for OAuth and a 99.9% uptime SLA on paid plans. Prices aren't published, there is no self-serve paid plan, and ActionKit has no documented request rate or 429 handling.
Windmill API + MCP
Token scopes reach a single script path with expiry, and a release ships most days under a published backward-compatibility policy. The default MCP URL puts the token in ?token= unless a superadmin turns that off, and ten CVEs were published in the past 12 months, several only by third parties.
Before you call either
Paragon ActionKit + MCP
- Sign a short-lived User Token per end user on your server, narrow it with the JWT Permissions claim, and never let the model see the signing key
- Set
NODE_ENV=productionbefore exposing the MCP server anywhere but localhost - Fetch the tool list once per session with
categoriesset, and cache it - Treat
nextPageCursoras an opaque string and stop paging when it is null, false or empty - Run Tool returns 200 and drops parameters not on the tool schema, so check names against the schema before calling
Windmill API + MCP
- Give the agent a token scoped to
jobs:runon one folder rather than a full user token - Connect over the OAuth gateway or send the token in a header so it stays out of logs
- With a multi-workspace token, pass
workspace_idon every workspace tool - Call
searchDocsbefore guessing at a flag or config key, thenreadDocsPagewith the returned URL - Poll the job by ID after
runScriptByPathfor long jobs instead of waiting on the call - On self-hosted Community Edition, turn off telemetry in instance settings if the base URL and usage counts must stay private
Questions
Which is better for AI agents, Paragon ActionKit + MCP or Windmill API + MCP?
Paragon ActionKit + MCP scores 50.3 (D) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on agent ergonomics, payments & pricing, maintenance & community and transparency & trust.
Do Paragon ActionKit + MCP and Windmill API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Paragon ActionKit + MCP and Windmill API + MCP without installing anything?
Yes. Paragon ActionKit + MCP has a hosted endpoint at https://actionkit.useparagon.com and Windmill API + MCP at https://app.windmill.dev/api.
Are Paragon ActionKit + MCP and Windmill API + MCP open source?
No open-source release is listed for Paragon ActionKit + MCP. Windmill API + MCP is open source (AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts).
Other comparisons with Paragon ActionKit + MCP or Windmill API + MCP
- Activepieces API + MCP vs Paragon ActionKit + MCP
- Activepieces API + MCP vs Windmill API + MCP
- Microsoft Copilot Studio MCP vs Paragon ActionKit + MCP
- Microsoft Copilot Studio MCP vs Windmill API + MCP
- Gumloop vs Paragon ActionKit + MCP
- Gumloop vs Windmill API + MCP
- Kestra vs Paragon ActionKit + MCP
- Kestra vs Windmill API + MCP
- Kognitos vs Paragon ActionKit + MCP
- Kognitos vs Windmill API + MCP
- Make API + MCP vs Paragon ActionKit + MCP
- Make API + MCP vs Windmill API + MCP
- Cooper (Mandl) vs Paragon ActionKit + MCP
- Cooper (Mandl) vs Windmill API + MCP
- Motive Agents vs Paragon ActionKit + MCP
- Motive Agents vs Windmill API + MCP
- n8n API + MCP vs Paragon ActionKit + MCP
- n8n API + MCP vs Windmill API + MCP
- Node-RED vs Paragon ActionKit + MCP
- Node-RED vs Windmill API + MCP
- Paragon ActionKit + MCP vs Microsoft Power Automate
- Pipedream API + MCP vs Windmill API + MCP
- Microsoft Power Automate vs Windmill API + MCP
- Prismatic vs Windmill API + MCP
- Tray.ai API + MCP vs Windmill API + MCP
- Windmill API + MCP vs Workato API + MCP
- Paragon ActionKit + MCP vs Pipedream API + MCP
- Paragon ActionKit + MCP vs Prismatic
- Paragon ActionKit + MCP vs Tray.ai API + MCP
- Paragon ActionKit + MCP vs Workato API + MCP
Machine-readable
- This page as Markdown
/compare/paragon-vs-windmill.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/paragon.json·/api/v1/tools/windmill.json - From a terminal
anchor compare paragon windmill(the CLI) - Over MCP
compare_tools {"a": "paragon", "b": "windmill"}at/mcp, no key