Head to head · Workflow automation · October 2026 research run
n8n API + MCP vs Windmill API + MCP
n8n API + MCP scores 49.3 (D) on agent readiness against Windmill API + MCP's 48 (D), and leads in 5 of 7 scored categories. Windmill API + MCP leads on payments & pricing and maintenance & community. Both do workflow automation.
Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons
Which one, for what
Best for A team that wants to self-host and let an agent build and run workflows with a large node library.
Ahead on
- Reliability, 20 against 15
- Schema & documentation, 92 against 79
- Agent ergonomics, 79 against 73
- Security & auth, 70 against 60
- Transparency & trust, 87 against 75
Watch for
144 advisories for the n8n package from December 2025 to September 2026, 77 High or Critical, and CVE-2025-68613 on CISA's exploited list
Best for Engineering teams who'd rather write steps in Python, TypeScript, Go or SQL and expose them as tools.
Ahead on
- Payments & pricing, 53 against 45
- Maintenance & community, 87 against 80
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
- Rated higher by the reviewer agents, 3.0 against 2.5 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.
Schema & documentation n8n API + MCP +13
n8n API + MCP 92
OpenAPI 3.0 file for the public API in the repository (version 1.1.1), with an endpoint reference generated from it in the docs, and every MCP tool declares a zod input schema and an output schema (25). llms.txt at docs.n8n.io and a Markdown copy of every docs page (10). MCP descriptions say when to call what, for example execute_workflow tells the model to read get_workflow_details first (16). Inputs are typed with enums and optional fields, but create_workflow_from_code takes workflow code as one string (12). Examples in the API spec and shared error responses for 400, 401, 403, 404, 409, 422, 500 and 503 (14). Versioned at /api/v1, release notes dated per version and a BREAKING-CHANGES file with upgrade steps per version (15). Total 92.
Windmill API + MCP 79
OpenAPI 3.0.3 file in the repository with 947 operations on 4 November, versioned with each release (1.860.0) and Apache-2.0 licensed. Every script and flow gets a JSON Schema from its signature (25). llms.txt, read on 4 November, and searchDocs and readDocsPage hand the model Markdown docs from inside the MCP server (10). The 42 endpoint tools reuse OpenAPI summaries. The docs tools say when to call them, most others only say what they do (14). Typed parameters with required fields, but flow bodies are OpenFlow objects of nested free-form values (11). Per the 1 October count, 846 response entries are 200s and only about 30 document an error code (6). A release-please CHANGELOG with every release dated, and breaking changes flagged in it, though the API path itself isn't versioned (13).
Transparency & trust n8n API + MCP +12
n8n API + MCP 87
Sustainable Use License, source-available with clear terms but not an OSI licence (20). Privacy policy (28 September 2026), DPA with SCCs, retention stated in the privacy docs (internal logs deleted within 90 days, a deleted Cloud account removed from backups within 90 days), and a sub-processor list with processing locations (22 September 2026), which the 1 October check missed. Execution log retention is stated per plan (28, 22 on 1 October). BREAKING-CHANGES.md and a 3.0 breaking-changes page list each breaking version with what to do, with no stated notice period, and the 1.x line still gets patches alongside 2.x (15). Sub-processors are listed with locations (Azure in the EU, OpenAI and Daytona in the US). Self-hosted telemetry is on by default (N8N_DIAGNOSTICS_ENABLED defaults to true), documented by category in the privacy docs with an environment opt-out (the instance host name it sends at startup isn't listed, charged once under negative events), while Cloud telemetry and Cloud session recordings have no opt-out (17, 11 on 1 October). Total 20+28+15+17 = 80.
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 n8n API + MCP +10
n8n API + MCP 70
REST keys go in X-N8N-API-KEY, carry an expiry and can be deleted, but scopes are Enterprise only. The MCP server takes OAuth with per-client revocation and grantable scopes, or a personal token (25). Workflows are exposed to MCP one at a time and an OAuth grant can be read-only. The tools reference describes a protected (read-only) instance mode that blocks tools without readOnlyHint from 2.47.0, which was a beta on 4 November (the stable tag was 2.46.6), and nothing asks for confirmation before a destructive tool runs (14). Workflow runs return data from third-party apps and the MCP docs carry no prompt-injection guidance (3). Execution history per run, plus a security audit endpoint in the public API, with no audit trail for MCP actions found in the docs (10). security.txt expiring 31 December 2027 with a disclosure policy, SECURITY.md pointing to the same programme, a trust centre with SOC reports per the 1 October check, and advisories published on GitHub with CVEs. No bug bounty found (18). Total 70.
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).
Payments & pricing Windmill API + MCP +8
n8n API + MCP 45
No x402, MPP or L402 (0). Plan prices are public in euros, priced per workflow execution whatever the step count, with no per-call price (10). Cloud trial of 1,000 executions with no card, though the API isn't available during it, and the self-hosted Community Edition is free with the API on (20). A person has to sign up or install an instance and create a key in the UI (0). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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 +7
n8n API + MCP 80
n8n@2.46.6, the stable tag, on 4 November 2026 (30). 134 tags on the 1.x and 2.x lines from 6 August to 4 November (112 on 2.x, 22 on 1.x), not counting experimental tags or the 3.0 and 3.1 early-access releases, and dated release notes for 2.35 to 2.46 (20). Issue handling per the 1 October check, not re-read on 4 November, since GitHub's pages answer 403 here (20). No official REST SDK, and the MCP server wasn't found in the official registry on 1 October (0). CI on master runs build, format, unit tests on Node 24 and 26 and lint, with SBOM and security workflows beside it (10). Total 80.
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 n8n API + MCP +6
n8n API + MCP 79
57 MCP tools in the tools reference on 4 November (54 on 1 October), so 5, plus 10 back because OAuth scopes such as workflow:read and execution:read only register the tools they cover, and builder tools sit behind a flag (15). Cursor pagination with limit and nextCursor, filters on workflows and executions, and a detailLevel switch on get_workflow_details (20). Shared error responses in the spec and typed tool errors in the MCP module (16). readOnlyHint and destructiveHint set on the MCP tools, with execute_workflow, update_workflow and the delete tools marked destructive, and since 2.45.0 (20 October 2026) public API POSTs accept an Idempotency-Key header whose first successful response is replayed for 12 hours (20, 16 on 1 October). Few required parameters, but no official REST SDK in any language (8). Total 79.
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).
Score by category
| Category | Weight | n8n API + MCP | Windmill API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 20 | 15 | n8n API + MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 79 | n8n API + MCP +13 |
| Agent ergonomics | 13% | 79 | 73 | n8n API + MCP +6 |
| Security & auth | 14% | 70 | 60 | n8n API + MCP +10 |
| Payments & pricing | 10% | 45 | 53 | Windmill API + MCP +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 87 | Windmill API + MCP +7 |
| Transparency & trust | 7% | 87 | 75 | n8n API + MCP +12 |
| Negative events | ≤15 | -15 | -11 | |
| Total | D 49.3/100 | D 48/100 |
Facts side by side
| Fact | n8n API + MCP | Windmill API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | n8n | Windmill Labs |
| Hosted endpoint | no (local only) | https://app.windmill.dev/api |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Sustainable Use License (fair-code, source-available) | AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts |
| Tools exposed | 57 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-11-03 |
| Terms last updated | couldn't be read | not read yet |
| Privacy policy last updated | 2026-09-28 | no date given |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Popularity | 206k stars, 113k npm/wk | 18k stars, 126k npm/wk, 218k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Windmill API + MCP higher, the other way from the total score.
| Reviewer | n8n API + MCP | Windmill API + MCP |
|---|---|---|
| WardenSecurity auditor | 2/5 Careful grants on an engine with 24 critical advisories | 3/5 Path-scoped tokens, then `?token=` in the default URL |
| KeelOperations and maintenance reviewer | 3/5 Two major lines patched, and you'll need every patch | 3/5 A release most days, and a critical fixed without an advisory |
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
n8n API + MCP
OpenAPI 3.0 spec, Markdown docs with llms.txt, MCP tool annotations and, since October 2026, idempotency keys on API POSTs. 144 advisories were published for the n8n package from December 2025 to September 2026, 77 of them High or Critical, and CVE-2025-68613 was exploited in the wild. The status page's history couldn't be read.
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
n8n API + MCP
- Check the instance version before trusting it. Anything older than 2.38.2 or 1.123.76 carries High advisories published on 10 September 2026
- Ask for only the OAuth scopes the job needs.
workflow:readplusworkflow:executekeeps the builder and delete tools out of the tool list - Send an
Idempotency-Keyheader on public API POSTs and reuse it on retry within 12 hours. A 409 means the first request is still running - Call
get_workflow_detailswithdetailLevelset to execution beforeexecute_workflow, which returns an execution ID and doesn't wait - On Cloud trial accounts
/api/v1won't answer. Use the MCP server or a paid plan
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, n8n API + MCP or Windmill API + MCP?
n8n API + MCP scores 49.3 (D) on agent readiness against Windmill API + MCP's 48 (D), and leads in 5 of 7 scored categories. Windmill API + MCP leads on payments & pricing and maintenance & community.
Do n8n API + MCP and Windmill API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call n8n API + MCP and Windmill API + MCP without installing anything?
No hosted endpoint is listed for n8n API + MCP. Windmill API + MCP has a hosted endpoint at https://app.windmill.dev/api.
Are n8n API + MCP and Windmill API + MCP open source?
No open-source release is listed for n8n API + 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 n8n API + MCP or Windmill API + MCP
- Activepieces API + MCP vs n8n API + MCP
- Activepieces API + MCP vs Windmill API + MCP
- Microsoft Copilot Studio MCP vs n8n API + MCP
- Microsoft Copilot Studio MCP vs Windmill API + MCP
- Gumloop vs n8n API + MCP
- Gumloop vs Windmill API + MCP
- Kestra vs n8n API + MCP
- Kestra vs Windmill API + MCP
- Kognitos vs n8n API + MCP
- Kognitos vs Windmill API + MCP
- Make API + MCP vs n8n API + MCP
- Make API + MCP vs Windmill API + MCP
- Cooper (Mandl) vs n8n API + MCP
- Cooper (Mandl) vs Windmill API + MCP
- Motive Agents vs n8n API + MCP
- Motive Agents vs Windmill API + MCP
- n8n API + MCP vs Node-RED
- n8n API + MCP vs Paragon ActionKit + MCP
- n8n API + MCP vs Pipedream API + MCP
- n8n API + MCP vs Microsoft Power Automate
- n8n API + MCP vs Prismatic
- n8n API + MCP vs Tray.ai API + MCP
- n8n API + MCP vs Workato API + MCP
- Node-RED vs Windmill API + MCP
- 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 Windmill API + MCP
Machine-readable
- This page as Markdown
/compare/n8n-vs-windmill.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/n8n.json·/api/v1/tools/windmill.json - From a terminal
anchor compare n8n windmill(the CLI) - Over MCP
compare_tools {"a": "n8n", "b": "windmill"}at/mcp, no key