# Make MCP server

> Run Make scenarios and manage scenarios, connections, webhooks, data stores and teams from your AI assistant.

- Listing: https://mcp.tc/i/make
- Connect: use the server's own URL `https://mcp.make.com` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Automation & Integrations](https://mcp.tc/c/automation)
- Vendor: Make
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage: <https://developers.make.com/mcp-server>

## About

Connects an AI assistant to a Make account. It can run active and on-demand scenarios, view and modify scenarios and related entities such as connections, webhooks and data stores, and view and modify teams and organizations.

The server is hosted by Make and uses streamable HTTP at https://mcp.make.com. You sign in with OAuth, or you can use an MCP token. Scopes chosen at connection time decide which tools are available. Scenario run tools are available on all plans, and management tools need a paid plan.

## What it can do

- Run active and on-demand Make scenarios
- View and modify scenarios
- Manage connections, webhooks and data stores
- View and modify teams and organizations
- Limit available tools through OAuth scopes

## Example prompts

- "Run my order sync scenario in Make now."
- "List the scenarios in my Make team."
- "Show the webhooks configured in my Make organization."
- "What tools do you have from the Make MCP server?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http make https://mcp.make.com
```

2. Start Claude Code, type `/mcp`, pick **make** and choose **Authenticate**. A browser window opens for the Make sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Make** and paste this URL:

```url
https://mcp.make.com
```

3. Click **Add**, then **Connect**, and sign in when Make asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Make&connectorUrl=https%3A%2F%2Fmcp.make.com>) (opens connector settings)

2. Check that the URL reads `https://mcp.make.com` and click **Add**.

3. Click **Connect** and sign in when Make asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.make.com` as the server URL and choose **OAuth**. ChatGPT sends you to Make to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=make&config=eyJ1cmwiOiJodHRwczovL21jcC5tYWtlLmNvbSJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "make": {
      "url": "https://mcp.make.com"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=make&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.make.com%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"make","type":"http","url":"https://mcp.make.com"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "make": {
      "type": "http",
      "url": "https://mcp.make.com"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "make": {
      "serverUrl": "https://mcp.make.com"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add make --url https://mcp.make.com
codex mcp login make
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.make]
url = "https://mcp.make.com"
```

### Gemini CLI

```bash
gemini mcp add --transport http make https://mcp.make.com
```

Then, inside Gemini CLI, run `/mcp auth make` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "make": {
      "type": "http",
      "url": "https://mcp.make.com"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.make.com`.

## Details

- Server version: 1.1.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-04

---
Source: https://mcp.tc/i/make (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report