All — pass MAKE_ZONE (eu1.make.com, us1.make.com, etc.) to match your org's region. Cross-region API calls do not work.

Does the agent see scenario data?

Only run-log output. Internal scenario step data may include sensitive values — review which scenarios you expose before granting access.

Can the agent author new scenarios?

No. Scenarios are authored in the Make visual editor; the MCP only triggers and inspects.

Yes — the API is available on Make Free, but with low rate limits. For agent-driven use on a team, expect to need a paid plan.

Make (Integromat)

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Trigger Make scenarios and inspect runs from an AI agent.

Score 70(?)Community (unofficial Make.com MCP)MIT 158Verified May 31, 2026Top MCPs for Automation & Workflows →

Install View on GitHub

Quick answer

What it does

Connects to a Make organisation, lists scenarios, runs them on demand, and reads execution status and run logs.

Best for

Triggering existing Make scenarios
Inspecting failed runs
Listing scenarios available to the agent
Integrating Make with other agent workflows

Not for

Authoring scenarios (use the Make visual builder)
High-frequency triggers (use Make webhooks directly)

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
        "MAKE_ZONE": "${MAKE_ZONE}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export MAKE_API_TOKEN=your-make-api-token
# export MAKE_ZONE=eu1.make.com
claude mcp add make -- npx -y make-mcp-server

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
        "MAKE_ZONE": "${MAKE_ZONE}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
        "MAKE_ZONE": "${MAKE_ZONE}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
        "MAKE_ZONE": "${MAKE_ZONE}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
        "MAKE_ZONE": "${MAKE_ZONE}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "make-mcp-server"
          ],
          "env": {
            "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
            "MAKE_ZONE": "${MAKE_ZONE}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.make]
command = "npx"
args = [
  "-y",
  "make-mcp-server",
]
env = { MAKE_API_TOKEN = "${MAKE_API_TOKEN}", MAKE_ZONE = "${MAKE_ZONE}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "make": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "make-mcp-server"
        ]
      },
      "env": {
        "MAKE_API_TOKEN": "${MAKE_API_TOKEN}",
        "MAKE_ZONE": "${MAKE_ZONE}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Make (Integromat) doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set MAKE_API_TOKEN, MAKE_ZONE in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope: Network
Sandbox: Make API token in env. Tokens are scoped to one organisation. Create a dedicated team member account for the MCP with access only to the scenarios it needs to trigger.
Gotchas: Make tokens have broad scope by default. Create a non-admin team-member account for the MCP.
Triggering paid-tier scenarios costs operations on every run — be aware of per-trigger cost.
Audit log per scenario is the forensic trail; review it after any agent-triggered run.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. automation & workflows work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-automation-workflows

Compare Make (Integromat) against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Make (Integromat) MCP vs [Zapier MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/make
- top-mcps.com listing for Zapier

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Make (Integromat) MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/make (fetch https://top-mcps.com/mcp/make.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (MAKE_API_TOKEN, MAKE_ZONE) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 31, 2026
Refreshed install snippets and fact sheet; verified for 2026.
May 10, 2025
Initial directory listing.

More Automation & Workflows MCPs

Other tools in the same category worth evaluating.

Zapier

Official

Expose 8,000+ Zapier integrations as tools your AI agent can call.

zapierautomationintegrationsworkflow

5 minLow

Make.com

Official

Turn Make.com on-demand scenarios into agent-callable tools — official MCP.

make-comautomationworkflowsintegromat

10 minMedium

Pipedream

Official

2,800+ apps and managed OAuth via Pipedream's hosted MCP at mcp.pipedream.com.

pipedreamautomationworkflowsoauth

10 minMedium

Compared with Make (Integromat)

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Make (Integromat)vsZapier Make (Integromat)vsPipedream Make (Integromat)vsn8n (MCP archived)Make (Integromat)vsIFTTT (MCP archived)

Exploring Top MCPs for Automation & Workflows? See all Automation & Workflows MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

Which Make regions?

Does the agent see scenario data?

Can the agent author new scenarios?

Free plan support?

What changed

More Automation & Workflows MCPs

Zapier

Make.com

Pipedream

Compared with Make (Integromat)