# Make.com

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

[Canonical HTML page](https://top-mcps.com/mcp/make-com) · [server.json](https://top-mcps.com/mcp/make-com.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

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

```json
{
  "mcpServers": {
    "make-com": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "${MAKE_API_KEY}",
        "MAKE_ZONE": "${MAKE_ZONE}",
        "MAKE_TEAM": "${MAKE_TEAM}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

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

```shell
# export MAKE_API_KEY=your_make_key
# export MAKE_ZONE=eu2.make.com
# export MAKE_TEAM=your_team_id
claude mcp add make-com -- npx -y @makehq/mcp-server
```

### Cursor — `.cursor/mcp.json`

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

```json
{
  "mcpServers": {
    "make-com": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "${MAKE_API_KEY}",
        "MAKE_ZONE": "${MAKE_ZONE}",
        "MAKE_TEAM": "${MAKE_TEAM}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

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

```jsonc
{
  "servers": {
    "make-com": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "${MAKE_API_KEY}",
        "MAKE_ZONE": "${MAKE_ZONE}",
        "MAKE_TEAM": "${MAKE_TEAM}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "make-com": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "${MAKE_API_KEY}",
        "MAKE_ZONE": "${MAKE_ZONE}",
        "MAKE_TEAM": "${MAKE_TEAM}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "make-com": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "${MAKE_API_KEY}",
        "MAKE_ZONE": "${MAKE_ZONE}",
        "MAKE_TEAM": "${MAKE_TEAM}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@makehq/mcp-server"
          ],
          "env": {
            "MAKE_API_KEY": "${MAKE_API_KEY}",
            "MAKE_ZONE": "${MAKE_ZONE}",
            "MAKE_TEAM": "${MAKE_TEAM}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

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

```shell
# ~/.codex/config.toml
[mcp_servers.make-com]
command = "npx"
args = [
  "-y",
  "@makehq/mcp-server",
]
env = { MAKE_API_KEY = "${MAKE_API_KEY}", MAKE_ZONE = "${MAKE_ZONE}", MAKE_TEAM = "${MAKE_TEAM}" }
```

### Zed — `~/.config/zed/settings.json`

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

```jsonc
{
  "context_servers": {
    "make-com": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@makehq/mcp-server"
        ]
      },
      "env": {
        "MAKE_API_KEY": "${MAKE_API_KEY}",
        "MAKE_ZONE": "${MAKE_ZONE}",
        "MAKE_TEAM": "${MAKE_TEAM}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Make.com 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.

```none

```

## At a glance

- **Maintainer:** Make.com
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** MAKE_API_KEY, MAKE_ZONE, MAKE_TEAM
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Make.com accounts
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-27
- **GitHub stars:** 158 (fetched 2026-06-02T11:55:52.262Z)
- **Score:** 75/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/integromat/make-mcp-server

## Quick answer

**What it does.** Discovers Make.com on-demand scenarios and exposes them as MCP tools at runtime, passing parsed inputs and returning JSON output.

**Best for:**
- Invoking existing Make scenarios from chat
- Returning structured JSON from a workflow
- Team-built automation surfaced to agents
- Multi-step ops behind a single tool
- EU-region accounts (set MAKE_ZONE)

**Not for:**
- Scenarios with non-on-demand triggers
- Workflows that need real-time event handling
- Cases where the agent itself should compose the workflow

## Description

The official Make.com MCP scans your Make account for scenarios scheduled "on demand," exposes each as an MCP tool with its parsed input parameters, and returns the scenario output as structured JSON.

## Why it matters

Make.com is one of the two dominant workflow automation platforms (alongside Zapier). The official MCP lets an agent invoke any user-built scenario without wrapper code.

## Key features

- Auto-discovery of on-demand scenarios
- JSON-typed input parameters
- Per-team scoping via MAKE_TEAM
- EU/US region support via MAKE_ZONE
- MIT, vendor-maintained

## FAQ

### Which scenarios are exposed?

Only those configured with the "On Demand" trigger. Time-triggered or webhook scenarios are not surfaced.

### EU or US?

Set `MAKE_ZONE` to your account's zone (e.g. `eu2.make.com` or `us1.make.com`).

### Required scopes?

API key must have `scenarios:read` and `scenarios:run` scopes.

## Changelog

- **2026-05-27** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-05-25** — Initial directory listing.