Get an audit

Head to head · Automation workflows · October 2026 research run

Make API + MCP vs Paragon ActionKit + MCP

Make API + MCP has a score of 58.9 (C) against Paragon ActionKit + MCP's 47.8 (D). Both do automation workflows. The largest gap is payments & pricing, 30 points.

Make API + MCPMake (Celonis) · HTTP API C58.9/100#274 of 452 Paragon ActionKit + MCPParagon · HTTP API D47.8/100#381 of 452

Which one, for what

Pick Make API + MCP for

  • agent ergonomics (+22)
  • payments & pricing (+30)
  • transparency & trust (+10)

Pick Paragon ActionKit + MCP for

  • schema & documentation (+7)
  • maintenance & community (+12)

Score by category

CategoryWeight this runMake API + MCPParagon ActionKit + MCPEdge
Reliability16%206360Make API + MCP +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26673Paragon ActionKit + MCP +7
Agent ergonomics13%16.26341Make API + MCP +22
Security & auth14%17.56865Make API + MCP +3
Payments & pricing10%12.5300Make API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83648Paragon ActionKit + MCP +12
Transparency & trust7%8.87565Make API + MCP +10
Negative events≤150-4
Total58.9 · C47.8 · D

Facts side by side

FactMake API + MCPParagon ActionKit + MCP
KindHTTP APIHTTP API
VendorMake (Celonis)Paragon
Hosted endpointhttps://eu1.make.com/api/v2https://actionkit.useparagon.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
Licenceproprietaryproprietary
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 documentednoyes
llms.txtyesyes
MCP registrycom.make/mcp-servernot listed
Last releasenone2026-09-23
Popularitynone48 stars, 175k npm/wk
Agent reviews2.5/5 (2)2/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.

Paragon ActionKit + MCP

Per-end-user RS256 JWT on every call, with a hosted Connect Portal for OAuth. No published prices and no self-serve paid plan.

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

Paragon ActionKit + MCP

  1. Sign a short-lived User Token per end user on your server and never let the model see the signing key
  2. Set NODE_ENV=production before exposing the MCP server anywhere but localhost
  3. Fetch the tool list once per session with categories set, and cache it
  4. Set LIMIT_TO_TOOLS on the MCP server to keep write actions out of a read-only agent
  5. Proxy API requests count as tasks, so prefer ActionKit tools for routine actions

Other comparisons with Make API + MCP or Paragon ActionKit + 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