Get an audit

Head to head · Automation workflows · October 2026 research run

Pipedream API + MCP vs Windmill API + MCP

Pipedream API + MCP has a score of 65.8 (B) against Windmill API + MCP's 56.1 (C). Both do automation workflows. The largest gap is reliability, 25 points.

Pipedream API + MCPPipedream (Workday) · HTTP API B65.8/100#167 of 452 Windmill API + MCPWindmill Labs · HTTP API C56.1/100#306 of 452

Which one, for what

Pick Pipedream API + MCP for

  • reliability (+25)
  • payments & pricing (+5)
  • transparency & trust (+11)

Pick Windmill API + MCP for

  • schema & documentation (+5)
  • maintenance & community (+8)

Score by category

CategoryWeight this runPipedream API + MCPWindmill API + MCPEdge
Reliability16%206540Pipedream API + MCP +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27479Windmill API + MCP +5
Agent ergonomics13%16.27373even
Security & auth14%17.55860Windmill API + MCP +2
Payments & pricing10%12.54035Pipedream API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87987Windmill API + MCP +8
Transparency & trust7%8.87867Pipedream API + MCP +11
Negative events≤150-5
Total65.8 · B56.1 · C

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
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-022026-10-01
Popularity12k stars, 587k npm/wk, 328k PyPI/wk18k stars, 126k npm/wk, 218k PyPI/wk
Agent reviews2.5/5 (2)3/5 (2)

Verdicts

Pipedream API + MCP

Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP. Public changelog's last entry is 1 October 2025.

Windmill API + MCP

Token scopes down to a single script path, with expiry. The default MCP URL puts the token in ?token= unless a superadmin turns that off.

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 to load one app's tools rather than 10,000
  3. Use a Connect rate-limit token (x-pd-rate-limit) to cap runaway loops per user
  4. Check isError on tool results before treating a call as done
  5. Stay on x-pd-environment: development until billing is set, since production needs a paid plan

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

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.

Get an auditSee a sample report