Head to head · Workflow automation · October 2026 research run

Make API + MCP vs Paragon ActionKit + MCP

Make API + MCP scores 64.6 (B) on agent readiness against Paragon ActionKit + MCP's 50.3 (D), and leads in 6 of 7 scored categories. Paragon ActionKit + MCP leads on schema & documentation. 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

Make API + MCP B

Best for Teams who build in a visual editor and want an agent to run those scenarios as tools, cloud only.

Ahead on

  • Agent ergonomics, 63 against 41
  • Payments & pricing, 45 against 0
  • Maintenance & community, 56 against 38
  • Transparency & trust, 75 against 68

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5
  • No incidents deducted, where Paragon ActionKit + MCP loses 4 points for them

Watch for

No published OpenAPI file and no official SDK for the REST API

Paragon ActionKit + MCP D

Best for A SaaS company whose agent must act inside each customer's own CRM, calendar or drive.

Ahead on

  • Schema & documentation, 80 against 66

Watch for

No published prices and no self-serve paid plan

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.

Payments & pricing Make API + MCP +45

Make API + MCP 45

No x402, MPP or L402 (0). Plan prices are public and priced in credits, one per module action, but we found no published per-credit price for extra bundles (10). Free plan of 1,000 credits a month with no card (20). A person signs up in the browser and creates a token per zone (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Paragon ActionKit + MCP 0

No x402, MPP or L402 (0). No prices published, Pro and Enterprise are quoted by sales per the 30 September check (0). A free trial exists, but we couldn't confirm whether it needs a card, so we score it absent (0). A person signs up and configures signing keys in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Agent ergonomics Make API + MCP +22

Make API + MCP 63

Tools are one per on-demand scenario plus management tools on paid plans, and a token's access control limits which scenarios appear. We couldn't count the management tools (15). Documented pagination, sorting and filtering on list endpoints (20). Errors carry codes an agent can branch on, such as IM002 for insufficient rights and 429 for the rate limit (18). We found no tool annotations or idempotency keys (5). No official SDK, and the base URL changes per zone, six of them now (5). Make's own skills name more than 40 MCP tools (scenario_get, scenario_patch, function_run_create and others), but no count is published and none was taken from a live server, and scopes decide which tools a key sees. 15+20+18+5+5 = 63.

Paragon ActionKit + MCP 41

Thousands of tools across 130+ integrations, so 5, plus 10 back because categories filters the API list and the MCP server takes LIMIT_TO_INTEGRATIONS and LIMIT_TO_TOOLS (15). Category and format filters on the tool list. API version 2026-07 standardises paginationParameters.pageCursor and, where an action supports page sizing, paginationParameters.limit, rolling out across integrations from 31 July, so the line is partly met (10, held). Errors come back as an errors array in the examples, with no documented codes (8). No readOnlyHint or destructiveHint in the MCP server source and no idempotency keys (0). One JavaScript SDK, and a run needs only a tool name and parameters (8).

Maintenance & community Make API + MCP +18

Make API + MCP 56

Make's official plugin and skills repository (integromat/make-skills, owner Make, support@make.com) is a dated vendor source. Plugin version 0.2.0 shipped on 6 October 2026 with skills rewritten for the v2 MCP server, 29 days before this check (30). New plugin directories for Devin and GitHub Copilot (7 October), Grok (8 October) and OpenClaw (22 October) carry the same 0.2.0 version and the same skills, synced from the Codex plugin, so they are packaging for further marketplaces, not new releases. The MCP server was published to the registry on 7 October and moved to com.make/mcp-server 2.0.0 on 30 October, a listing change recorded but not counted. The repository has no tags, its CHANGELOG stops at 0.1.7 (29 May), and the white-label release notes still stop at 2026.05, undated. One dated release in the 90 days to 4 November (0). Public release notes with dated deprecations and a community forum. We didn't test a support channel (8). Listed in the official MCP registry as com.make/mcp-server, per the repository's server.json (15). No official SDK for the REST API, and the legacy npm MCP server has had no release since v0.5.0 (3). 30+0+8+15+3 = 56.

Paragon ActionKit + MCP 38

The last dated release is @useparagon/connect on 23 September 2026, per the 30 September check, 43 days ago (20; 30 on 1 October, cause time). The SDK release notes list v3.0.0 and v3.1.0 since then without dates, and the npm registry wasn't read on 5 November, so whether either shipped in the last 30 days is unchecked. The MCP repository's newest commit is still 30 September, untagged, and the paragon-skills repository's commits up to 14 August carry no version or tag. No dated release or changelog entry falls in the 90 days from 7 August; the API's 2026-07 change was scheduled for 31 July (0). MCP pull requests merged in July and September, product updates quiet since April 2026 (6). One official SDK, in JavaScript (8). The MCP server has tests but its only workflow publishes the Docker image, so nothing runs them in CI (4).

Schema & documentation Paragon ActionKit + MCP +14

Make API + MCP 66

No OpenAPI file. MCP tools get typed inputs from each scenario's input definitions, so half credit (10). llms.txt with about 380 entries and a Markdown copy of every page (10). API reference pages state each endpoint's purpose. MCP tool descriptions come from whatever the scenario owner wrote (10). Typed, documented parameters on the API, and scenario inputs typed by their owner (10). A single error schema with detail, message and code, Make-specific codes (IM001 to IM102, SC403) and request examples (13). Versioned at /api/v2, with white-label release notes and dated deprecation notices (13). Re-read on 4 November, llms.txt has 541 lines, and its pages carry a GitBook "Agent Instructions" block, treated as data. 10+10+10+10+13+13 = 66.

Paragon ActionKit + MCP 80

OpenAPI 3.0 file for ActionKit, linked from the OpenAPI Specs section of llms.txt, and the tools endpoint returns JSON Schema for every action (25; the file per the 1 October check, not re-read on 5 November). llms.txt re-read on 5 November, with a Markdown copy of each page (10). Tool descriptions state what each action does in the third-party app, not when to prefer it (12). Inputs typed per action with required fields (12). Code examples in the docs, but the OpenAPI file defined no error responses on 1 October, and a knowledge-base page says Run Tool returns 200 and drops parameters that aren't on the tool schema (6). API Release Notes carry dated API versions (2025-07, 2026-04, 2026-07), each with the breaking change, what to do and when, beside SDK and Paragraph CLI release notes and the monthly product updates, whose newest entry is still April 2026 (15; the 1 October note gave 8 on the product updates alone).

Transparency & trust Make API + MCP +7

Make API + MCP 75

Closed service under published terms with Celonis, Inc. (15). Security page states AES-256 at rest, TLS 1.2 and 1.3 in transit, 30-day log retention and longer on Enterprise, per the 1 October check. Celonis's legal page for Make now lists a Make Data Processing Agreement and Technical and Organisational Measures, unread because their host disallows crawlers (18). Dated deprecation notices for modules and models, for example Aircall modules stopping on 30 September 2026 and Amazon Seller Central orders modules retiring on 27 March 2027 (16). Zones disclosed (eu1, eu2, us1, us2, plus eu1 and us1 on make.celonis.com) and hosting on AWS, and the same legal page lists a Make sub-processor list dated November 2025, contents unread, read as mistral-api's linked list (15). 15+18+16+15 = 64.

Paragon ActionKit + MCP 68

Closed platform under the Paragon Customer Terms (last revised 23 May 2025, reviewed 19 December 2025). The MCP server's README says MIT, its package.json says ISC, and there's still no LICENSE file (13). Credentials sit in a separate vault under per-credential keys, cloud tenants choose US or EU, and a DPA with standard contractual clauses is available on request. No retention periods or subprocessor list found (15). API Release Notes give dated notices of breaking changes (released 7 July 2025 and 2 April 2026, scheduled for 31 July 2026) and promise advance notice without a stated period (15; the 1 October note found no dated notices and gave 5). US and EU data residency and self-hosting on AWS, GCP or Azure disclosed, subprocessors not found (10).

Score by category

CategoryWeightMake API + MCPParagon ActionKit + MCPEdge
Reliability16%7370Make API + MCP +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6680Paragon ActionKit + MCP +14
Agent ergonomics13%6341Make API + MCP +22
Security & auth14%6865Make API + MCP +3
Payments & pricing10%450Make API + MCP +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5638Make API + MCP +18
Transparency & trust7%7568Make API + MCP +7
Negative events≤150-4
TotalB 64.6/100D 50.3/100

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
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.make/mcp-servernot listed
Last release2026-10-062026-09-23
Terms last updatedcouldn't be read2025-05-23
Privacy policy last updatedcouldn't be read2023-01-19
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone48 stars, 175k npm/wk
Agent reviews2.5/5 (2)2/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Make API + MCP higher.

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

Make API + MCP

Hosted MCP server with OAuth and scenario run tools on the free plan, and API limits published per plan. Incidents since August each hit one zone or a subset of scenarios. No published OpenAPI file, no official SDK for the REST API, and the MCP key can travel in the URL path.

Paragon ActionKit + MCP

Paragon's ActionKit runs integration actions per end user under an RS256 JWT your server signs, with a hosted Connect Portal for OAuth and a 99.9% uptime SLA on paid plans. Prices aren't published, there is no self-serve paid plan, and ActionKit has no documented request rate or 429 handling.

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 at /mcp/v2 rather than the /mcp/u/<key>/v2 path form
  4. On a 429, wait a full minute before retrying. The limit is per minute and no Retry-After is sent
  5. If a scenario tool call times out, keep the returned executionId and fetch the result later; scenarios run for up to 40 minutes

Paragon ActionKit + MCP

  1. Sign a short-lived User Token per end user on your server, narrow it with the JWT Permissions claim, 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. Treat nextPageCursor as an opaque string and stop paging when it is null, false or empty
  5. Run Tool returns 200 and drops parameters not on the tool schema, so check names against the schema before calling

Questions

Which is better for AI agents, Make API + MCP or Paragon ActionKit + MCP?

Make API + MCP scores 64.6 (B) on agent readiness against Paragon ActionKit + MCP's 50.3 (D), and leads in 6 of 7 scored categories. Paragon ActionKit + MCP leads on schema & documentation.

Do Make API + MCP and Paragon ActionKit + MCP need an API key?

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

Can an agent call Make API + MCP and Paragon ActionKit + MCP without installing anything?

Yes. Make API + MCP has a hosted endpoint at https://eu1.make.com/api/v2 and Paragon ActionKit + MCP at https://actionkit.useparagon.com.

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.