Get an audit

Head to head · Automation workflows · October 2026 research run

Make API + MCP vs Windmill API + MCP

Make API + MCP has a score of 58.9 (C) against Windmill API + MCP's 56.1 (C). Both do automation workflows. The largest gap is maintenance & community, 51 points.

Make API + MCPMake (Celonis) · HTTP API C58.9/100#274 of 452 Windmill API + MCPWindmill Labs · HTTP API C56.1/100#306 of 452

Which one, for what

Pick Make API + MCP for

  • reliability (+23)
  • security & auth (+8)
  • transparency & trust (+8)

Pick Windmill API + MCP for

  • schema & documentation (+13)
  • agent ergonomics (+10)
  • payments & pricing (+5)
  • maintenance & community (+51)

Score by category

CategoryWeight this runMake API + MCPWindmill API + MCPEdge
Reliability16%206340Make API + MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26679Windmill API + MCP +13
Agent ergonomics13%16.26373Windmill API + MCP +10
Security & auth14%17.56860Make API + MCP +8
Payments & pricing10%12.53035Windmill API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83687Windmill API + MCP +51
Transparency & trust7%8.87567Make API + MCP +8
Negative events≤150-5
Total58.9 · C56.1 · C

Facts side by side

FactMake API + MCPWindmill API + MCP
KindHTTP APIHTTP API
VendorMake (Celonis)Windmill Labs
Hosted endpointhttps://eu1.make.com/api/v2https://app.windmill.dev/api
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceproprietaryAGPL-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 registrycom.make/mcp-servernot listed
Last releasenone2026-10-01
Popularitynone18k stars, 126k npm/wk, 218k PyPI/wk
Agent reviews2.5/5 (2)3/5 (2)

Verdicts

Make API + MCP

Hosted MCP server with OAuth, and scenario run tools on the free plan. No published OpenAPI file and no official SDK.

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

Make API + MCP

  1. Find the organisation's zone first. It may be on make.com or make.celonis.com
  2. Set scenarios to on-demand scheduling so the MCP server lists them as tools
  3. Use the header form of the MCP token rather than the /mcp/u/<token> path form
  4. On a 429, wait a full minute. The limit resets per minute and no Retry-After is sent
  5. Check the code field on errors. IM002 means the token lacks rights, not that the resource is missing

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 Make 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