Head to head · Workflow automation · October 2026 research run

Pipedream API + MCP vs Windmill API + MCP

Pipedream API + MCP scores 72.8 (BB) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on schema & documentation and maintenance & community. Both do workflow 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

Pipedream API + MCP BB

Best for Best when an agent acts in many third-party apps on behalf of your own users and you don't want to run OAuth yourself.

Ahead on

  • Reliability, 82 against 15
  • Security & auth, 66 against 60
  • Payments & pricing, 60 against 53

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Windmill API + MCP loses 11 points for them

Watch for

Public product changelog's last entry is 1 October 2025

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

  • Schema & documentation, 79 against 74
  • Maintenance & community, 87 against 79

Also in its favour

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

Reliability Pipedream API + MCP +67

Pipedream API + MCP 82

Atlassian Statuspage at status.pipedream.com with components for the REST and Connect APIs, event sources, workflows, frontends and integrations (20). history.atom, read on 1 November, has one incident in the 90 days from 3 August, a string.com chat problem on 5 October that the vendor says left 'all pipedream.com services and workflows' unaffected, so none touches the API. The 28 and 29 July HTTP trigger incidents left the window on 27 and 28 October, so the record is clean (30). Connect API limits are published with numbers, 3,500 token requests per 5 minutes per OAuth client, 2,000 account calls and 3,000 component listings per 5 minutes per project and 5,000 combined project-management calls, but none for action runs or tool calls (12). The rate-limits page, re-read on 1 November, documents 429 Too Many Requests with Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset and says to wait for the window and back off exponentially, with no idempotency keys or safe-retry guidance for action runs, which write to third-party apps (10 of 15). The pricing page lists 'SLAs' and priority support on Business with no figure or SLA document (0). Connect API and MCP server are generally available (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).

Maintenance & community Windmill API + MCP +8

Pipedream API + MCP 79

TypeScript SDK v3.3.0 and Python SDK v2.3.0 tagged on 21 October 2026, 11 days before this check (30). In the 90 days from 3 August the TypeScript SDK tagged v3.1.3 (18 August), v3.1.4, v3.1.5, v3.1.6, v3.2.0 and v3.3.0, and the Python SDK v2.1.19, v2.1.20, v2.2.0 and v2.3.0 (20). The public product changelog hasn't moved since 1 October 2025, though the components repository took 261 commits from 3 August to 30 October 2026 (7). Current official SDKs in TypeScript, Python and Java (15). SDKs are generated with Fern and the components repository has CI, but we didn't confirm test runs (7).

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

Payments & pricing Pipedream API + MCP +7

Pipedream API + MCP 60

No x402, MPP or L402 (0). Per-unit prices are public. One credit is 30 seconds of compute at 256 MB, extra credits cost $0.012, and end users beyond 100 cost $2 each on Startup (20). Free plan with no card, limited to development (20). A person signs up and creates an OAuth client in the browser (0). 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.

Security & auth Pipedream API + MCP +6

Pipedream API + MCP 66

OAuth client credentials exchanged for bearer tokens that expire after an hour, with scopes such as connect:accounts:read, connect:actions:* and connect:proxy (default *), clients that sign private key JWTs instead of holding a secret, secret rotation and two-key rotation, and client credentials in the query string refused with 400, per the authentication page read on 1 November. Short-lived Connect tokens per end user take a subset of the scopes, and the end-user MCP server signs in with OAuth (30; the 1 October note found no scopes, 22). Tools are fenced per app and per external user, and rate-limit tokens cap each user. Scopes narrow the management API, but connect:actions:* is all or nothing, so there is no read-only action mode and no confirmation before writes (10). Actions return third-party content such as email bodies with no prompt-injection guidance found (3). Per-run event history and logs, and no operator audit log found in the docs (8). SOC 2 Type 2 report on request, HIPAA BAA, annual penetration test, security@pipedream.com with a PGP key and a SECURITY.md. No bug bounty, and pipedream.com/.well-known/security.txt answered an HTML page on 1 November, so no security.txt (15).

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

Schema & documentation Windmill API + MCP +5

Pipedream API + MCP 74

OpenAPI file at pipedream_openapi_swagger.json per the 30 September check, and every MCP tool carries a JSON Schema built from the component's props (25). llms.txt per the 30 September check (10). Component descriptions state what the action does and link the upstream API docs, rarely when not to use it (12). Props are typed with options and required flags, though custom request actions take free-form JSON (11). Tool failures come back with isError and an attribution of where the error came from. Interactive API reference with examples (9). The API is under /v1 and the SDKs follow semver, but the public changelog's last entry is 1 October 2025 (7).

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

Score by category

CategoryWeightPipedream API + MCPWindmill API + MCPEdge
Reliability16%8215Pipedream API + MCP +67
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7479Windmill API + MCP +5
Agent ergonomics13%7373even
Security & auth14%6660Pipedream API + MCP +6
Payments & pricing10%6053Pipedream API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7987Windmill API + MCP +8
Transparency & trust7%7575even
Negative events≤150-11
TotalBB 72.8/100D 48/100

Facts side by side

FactPipedream API + MCPWindmill API + MCP
KindHTTP APIHTTP API
VendorPipedream (Workday)Windmill Labs
Hosted endpointhttps://api.pipedream.com/v1https://app.windmill.dev/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicencePipedream Source Available License (components)AGPL-3.0 (core), Apache-2.0 (clients and OpenAPI), commercial for enterprise-only parts
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-212026-11-03
Terms last updatedno date givennot read yet
Privacy policy last updated2026-02-02no date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity12k stars, 587k npm/wk, 328k PyPI/wk18k stars, 126k npm/wk, 218k PyPI/wk
Agent reviews2.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.

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

Pipedream API + MCP

Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP, with scoped OAuth clients and documented 429 handling. The public product changelog's last entry is 1 October 2025, and action runs have no published rate limit or retry-safety guidance.

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

Pipedream API + MCP

  1. Pass your own user ID as x-pd-external-user-id so each user's accounts stay separate
  2. Send x-pd-app-slug (required) so the MCP server loads one app's tools
  3. Request only the scopes you need when minting an OAuth token. The default is *
  4. On a 429, wait for Retry-After and check whether an action already ran before retrying a write
  5. Check isError on tool results before treating a call as done

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, Pipedream API + MCP or Windmill API + MCP?

Pipedream API + MCP scores 72.8 (BB) on agent readiness against Windmill API + MCP's 48 (D), and leads in 3 of 7 scored categories. Windmill API + MCP leads on schema & documentation and maintenance & community.

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

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

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

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

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

No open-source release is listed for Pipedream 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 Pipedream 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.