Head to head · Workflow automation · October 2026 research run

Activepieces API + MCP vs Windmill API + MCP

Activepieces API + MCP scores 59.3 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 5 of 7 scored categories. Windmill API + MCP leads on maintenance & community. Both do workflow automation.

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

Which one, for what

Activepieces API + MCP C

Best for A team that wants an MIT-licensed builder it can self-host or embed, with an agent that builds flows through MCP.

Ahead on

  • Reliability, 65 against 15
  • Payments & pricing, 60 against 53

Also in its favour

  • Free to start without a card

Watch for

Docs say API keys come from the platform dashboard in Platform and Enterprise editions, while the pricing page lists API access on every plan

Windmill API + MCP D

Best for Engineering teams who'd rather write steps in Python, TypeScript, Go or SQL and expose them as tools.

Ahead on

  • Maintenance & community, 87 against 80

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 Activepieces API + MCP +50

Activepieces API + MCP 65

Better Stack status page at status.activepieces.com with two components, API Health and Worker Health (20). Its feed shows no incident in the 90 days from 6 August 2026; the 26 July Worker Health incident has left the window, so a clean record (30). No request-rate limit for the API was found. The limits page gives run, memory, concurrency (5 to 30 concurrent runs per project by plan), webhook and storage limits with numbers, which aren't request rate limits, so the line is partly met and keeps its earlier 5 of 15 pending a rule on in-between values. No 429 or backoff guidance found (0). The terms set a 48-hour first-response support SLA on Business and Platform plans and no availability SLA (0). API and MCP server are generally available (10). 20 + 30 + 5 + 0 + 0 + 10 = 65.

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 Activepieces API + MCP +7

Activepieces API + MCP 60

No x402, MPP or L402 (0). Plan prices and $0.007 per extra credit are public, and the pricing page now says what a credit buys (a run is one credit however many steps, AI steps 2, 10 or 20 credits by model tier, agentic actions 1) (20, was 15). Free plan of 1,000 credits a month, no card and no time limit (20). A person signs up in the browser or installs an instance (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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

Activepieces API + MCP 80

0.92.3 tagged on 12 October 2026, with hotfix tags 0.92.3-hotfix.1 (23 October) and -hotfix.2 (28 October) (30). 18 stable tags from 0.88.0 (12 August) to 0.92.3 in the 90 days from 6 August (20). Per the 1 October check, not re-read on 4 November, 381 open issues labelled by area and priority, reply times unread (15). An embed SDK on npm, but no official REST SDK and no entry in the official MCP registry found, so the line is partly met and keeps its earlier 5 of 15 pending a rule on in-between values. CI runs typecheck, build, unit, API and end-to-end tests, plus DAST and a breaking-change check (10). 30 + 20 + 15 + 5 + 10 = 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).

Score by category

CategoryWeightActivepieces API + MCPWindmill API + MCPEdge
Reliability16%6515Activepieces API + MCP +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8379Activepieces API + MCP +4
Agent ergonomics13%7073Windmill API + MCP +3
Security & auth14%6460Activepieces API + MCP +4
Payments & pricing10%6053Activepieces API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8087Windmill API + MCP +7
Transparency & trust7%7775Activepieces API + MCP +2
Negative events≤15-11-11
TotalC 59.3/100D 48/100

Facts side by side

FactActivepieces API + MCPWindmill API + MCP
KindHTTP APIHTTP API
VendorActivepiecesWindmill Labs
Hosted endpointhttps://cloud.activepieces.com/api/v1https://app.windmill.dev/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (core), commercial licence for enterprise-only partsAGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts
Tools exposed47none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-122026-11-03
Terms last updatedcouldn't be readnot read yet
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelscouldn't be readnot read yet
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Popularity25k stars, 452k npm/wk18k stars, 126k npm/wk, 218k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

Activepieces API + MCP

MIT core, self-hostable, with an MCP server whose 47 tools all carry read-only or destructive annotations and a free Cloud plan with no card. The OpenAPI file documents no errors and no request rate limits are published, and eight advisories from July and August 2026 were followed by October piece fixes for SSRF and a password leak with no advisory.

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

Activepieces API + MCP

  1. Run ap_validate_flow before publishing a flow
  2. Use ap_search_actions with a plain task description rather than listing pieces
  3. Turn off the Flow Building and Tables groups for a project the agent should only read
  4. Page with limit and cursor and stop when next is null
  5. Cloud runs stop at 10 minutes of active time. Waits and approvals don't count

Windmill API + MCP

  1. Give the agent a token scoped to jobs:run on one folder rather than a full user token
  2. Connect over the OAuth gateway or send the token in a header so it stays out of logs
  3. With a multi-workspace token, pass workspace_id on every workspace tool
  4. Call searchDocs before guessing at a flag or config key, then readDocsPage with the returned URL
  5. Poll the job by ID after runScriptByPath for long jobs instead of waiting on the call
  6. 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, Activepieces API + MCP or Windmill API + MCP?

Activepieces API + MCP scores 59.3 (C) on agent readiness against Windmill API + MCP's 48 (D), and leads in 5 of 7 scored categories. Windmill API + MCP leads on maintenance & community.

Do Activepieces API + MCP and Windmill API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Activepieces API + MCP and Windmill API + MCP without installing anything?

Yes. Activepieces API + MCP has a hosted endpoint at https://cloud.activepieces.com/api/v1 and Windmill API + MCP at https://app.windmill.dev/api.

Are Activepieces API + MCP and Windmill API + MCP open source?

Yes. Activepieces API + MCP is open source (MIT (core), commercial licence for enterprise-only parts). Windmill API + MCP is open source (AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts).

Other comparisons with Activepieces API + MCP or Windmill API + MCP

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.