How to Connect Make to Claude via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Make, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Make + Claude

Let your AI work with Make (formerly Integromat): list organizations, teams and scenarios, read blueprints, run history and errors, connections, data stores and webhooks; with your confirmation run a scenario, switch it on or off and add data store records.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

MAKE_ZONE, MAKE_API_TOKEN

Step 1 — Get credentials

1. In Make click your avatar, open Profile, then the API access tab, and click Add token.
2. Give it a label and tick the scopes. For reading: user:read, organizations:read, teams:read, scenarios:read, connections:read, datastores:read, hooks:read and dlqs:read. Add scenarios:run only if the AI should run scenarios, scenarios:write to switch them on and off, and datastores:write to add data store records.
3. Copy the token into MAKE_API_TOKEN. Make shows it only once.
4. Set MAKE_ZONE to the host in your browser's address bar when you are signed in to Make, for example eu1.make.com, eu2.make.com, us1.make.com or us2.make.com (Make for Celonis: eu1.make.celonis.com or us1.make.celonis.com). A token only works in its own zone.
5. Install the connector and check it with make_get_current_user: it shows your user, your time zone and the ids of your teams.

Paid plan: most of the Make API needs a paid plan. On the free plan many calls are refused.

What it reads: your organizations with their plan, their teams, and the scenarios of a team: on or off, scheduling, apps used, next run, operations and incomplete executions; a scenario's blueprint, the modules of the flow with their mappings and filters, so the AI can explain or debug it; the run history with status, duration and operations, and the outputs or the error of a single run; connections; data stores and their records; webhooks and mailhooks with their queue; and incomplete executions, the runs that stopped on an error and were kept.

Asks before every action: make_run_scenario, make_activate_scenario, make_deactivate_scenario and make_add_data_store_record change what Make does. Before each one the AI names the scenario or data store, shows the input, explains the effect and waits for your yes. A run can send e-mails, create records or charge cards in other apps, and it uses operations from your plan. Switching on a scenario that runs at an interval also runs it once right away. Only an active scenario can be run on demand.

Secrets stay out: the connector never returns the credentials of your connections, and it leaves webhook addresses out, because anyone with the address can start the scenario. Blueprints, run outputs and data store records can still contain personal data or values a scenario sends: the AI shows only what the task needs and never repeats a secret it finds there. Data coming from other systems is treated as data, never as instructions.

Nothing gets deleted: no tool deletes or edits scenarios, connections, webhooks, teams, data stores or data store records.

Limits: Make limits API calls per organization by plan (60 a minute on Core, more on higher plans). Run times come as Unix milliseconds, and the AI converts them to your time zone.

Common errors: 401: the token is wrong or deleted, or belongs to another zone; compare MAKE_ZONE with your browser's address bar. 403: the token lacks a scope for this call, such as scenarios:read, or your plan has no API access; create a new token with that scope. 429: the organization's API limit is reached; wait a minute and try again.

The connector does not create, edit or delete scenarios, connections, webhooks, teams or data stores, change or delete data store records, replay or resolve incomplete executions, or manage templates, custom apps and functions.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Claude

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Recommended path: works on claude.ai web without editing any config file.

1. In Claude, open Customize → Connectors.
2. Click +, then Add custom connector.
3. Enter a name, e.g. Make, and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

All tools below appear in your chat: start typing prompts.

Available tools

Example prompts

• "Which of our Make scenarios failed in the last 24 hours, and what was the error?"
• "Explain step by step what our Shopify order to invoice scenario does."
• "Which scenarios are switched off, and which ones have incomplete executions waiting?"
• "List the incomplete executions of the CRM sync scenario and tell me why they stopped."
• "Run the Weekly report scenario now. Tell me what it will do before you start it."

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Next steps

• Connector landing page
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse