Independent review. Unpaid; no partnership with Make. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Visual builder for multi-step automation scenarios across apps, billed in credits. A hosted MCP server lets AI clients such as Claude and ChatGPT run scenarios, and scenarios can be exported and imported as JSON blueprints.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Visual builder for multi-step automation scenarios across apps, billed in credits. A hosted MCP server lets AI clients such as Claude and ChatGPT run scenarios, and scenarios can be exported and imported as JSON blueprints.
Differentiation
Documented fit: Multi-step, branching scenarios built visually; Running Make scenarios from an AI client over MCP. Uniqueness is not established.
Replaceability and switching
Compare n8n, Zapier. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Teams seeking a single flat charge per scenario run regardless of actions or model usage. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
Teams seeking a single flat charge per scenario run regardless of actions or model usage
Top use cases
Multi-step, branching scenarios built visually
Running Make scenarios from an AI client over MCP
To verify Drawn from our draft verdict; sourced use cases to come.
In depth
Plans
The Free plan includes 1,000 monthly credits. Paid pricing varies with credit volume and billing term; annual prepayment is discounted. Exact paid prices could not be confirmed from the current rendered price cards, so check the current quote before budgeting. Checked 2026-10-18. source ↗
Make MCP
Make's hosted MCP server lets AI clients such as Claude and ChatGPT run scenarios and, on paid plans, view and modify scenarios, connections, webhooks and data stores. Connect with OAuth or an MCP token. source ↗
Credits
Most actions consume one credit; advanced AI features can use more. Routers and listed error-handler modules are exceptions that do not consume credits. Credits expire at the end of their term, and scenarios pause when credits run out unless additional credits are purchased. source ↗
Blueprints
Scenarios export as .json blueprints that can be imported into a new scenario (under 2 MB) or copied as JSON text to paste elsewhere. Connections are reconfigured after import. source ↗
API access
Most REST API endpoints require a paid plan and an authentication token with the relevant scopes. MCP scenario-run tools are available on all plans, while management tools require paid access. source ↗
Long-running scenarios
An MCP timeout does not necessarily stop the scenario. Make documents continued execution for up to 40 minutes and returns an execution ID for retrieving results; check that run before starting another. source ↗
How to use it with AI
How Make connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedVerify which side exports and which imports, supported formats and permissions. Make's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route.Make file docs ↗Claude (incl. Claude Code) file docs ↗
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Make publishes an API, but this pairing still needs network, authentication and execution-scope checks.Make API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Make is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Make's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.Make file docs ↗OpenAI Codex file docs ↗
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Make is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Make's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Make file docs ↗Google Antigravity file docs ↗
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
To verify Exact paid price amounts and billing-term mapping require current checkout confirmation; live page did not render the price cards in this review.
Workflow automation with a no-license-fee self-hosted Community Edition and paid Cloud plans. The MCP Server Trigger exposes connected tools and workflows to MCP clients. Self-hosting still requires infrastructure, maintenance and compliance with n8n's license.
App-to-app automation across what Zapier says are 9,000+ apps, with Zaps, Tables and Forms. Zapier MCP lets AI assistants take actions (Zapier cites 40,000+); each successful MCP call uses two tasks from your plan.