Make MCP server allows external AI systems, such as AI agents, to discover your scenarios and perform tasks for you using those scenarios. Model Context Protocol (MCP) is a communication standard between AI systems and external systems. It enables these systems to easily and safely interact by defining endpoints and providing authentication.

Benefits

• Turns your scenarios into callable tools for AI

• Creates bidirectional communication between AI and scenarios

• Takes advantage of automation logic in Make to give capabilities to AI

How does Make MCP server work?

Make MCP server connects Make to external AI systems in two key ways: exposing all your scenarios scheduled On demand to AI, and allowing AI to run these scenarios as tools. These functions (listing available scenarios and triggering their execution) have their own endpoints, or URLs that allow access to resources from a web service.

You can help your AI system understand what data to receive and send when it uses scenarios as tools by configuring scenario inputs and outputs:

• Inputs: parameters your AI fills with data when the scenario runs

• Outputs: data returned from the scenario to your AI

Available Make MCP servers

We currently allow two ways to integrate Make MCP server:

Make Cloud MCP Server (recommended)

The cloud-based MCP server, hosted by Make, runs via Server-Sent Events (SSE). It is suitable for any integration and environment.

Make Local MCP Server (legacy)

The local MCP server is a basic version that runs locally on your machine. It is ideal for scenarios that require local management and control, and when you have significant technical expertise.

Hosted by Make, the cloud-based Make MCP server runs via Server-Sent Events (SSE). SSE is a web standard for servers to send updates to clients over HTTP.

Features

• Ideal for cloud-based solutions or setups without direct server access

• Allows integration with Make scenarios through SSE endpoints

• No local installation needed

Prerequisites

• Make MCP Token (see Obtaining MCP Token)

• At least one available Make scenario with On demand scheduling

• MCP-compatible client (e.g., Cursor App or Claude Desktop App)

Installation and usage by client type

Client with SSE support (e.g., Cursor)

If your client supports SSE, use the following endpoint:

https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse

Configuration example:

{
  "mcpServers": {
    "make": {
      "url": "https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse"
    }
  }
}

Replace <MAKE_ZONE> and <MCP_TOKEN> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MCP_TOKEN - You can generate your MCP token in your Make profile.

Client with authorization in headers support

If your client supports sending authorization in HTTP headers, you can use the following URL:

https://<MAKE_ZONE>/mcp/api/v1/sse

Specify the MCP token in the Authorization header as follows:

Authorization: Bearer <MCP_TOKEN>

Clients without SSE support (e.g., Claude Desktop)

Use the Cloudflare mcp-remote proxy for compatibility. Refer to Cloudflare's MCP Remote Proxy Guide for more details.

Configuration example:

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse"
      ]
    }
  }
}

Replace <MAKE_ZONE> and <MCP_TOKEN> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MCP_TOKEN - You can generate your MCP token in your Make profile.

MCP URL customization

You can append the following advanced query parameters to the MCP URL for a more customized experience:

• ?maxToolNameLength=<length> - By default, generated tool names are cropped to a maximum of 56 characters to ensure compatibility with most AI systems. You can customize this behavior by specifying the maximum generated tool name length using this parameter. The allowed range is 32 to 160 characters.

An MCP token is an API key that allows external AI systems to access your scenarios as callable tools.

To obtain an MCP token:

1. At the bottom of the left sidebar in your Make account, click your name.

2. Click Profile.

3. Navigate to the API access tab.

4. In Tokens, click Add token, which opens a dialog.

5. Choose the scopes, including the mcp:use scope if you want to make your scenarios available as tools.

6. In Label, name your MCP token.

7. Click Add.

You have now generated an MCP token for your MCP client.

By default, your MCP token grants AI systems access to all of your tools in Make, across every organization you belong to. You can append query parameters to the MCP URL to restrict tool access to the following levels:

Organization level

https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse?organizationId=<id>

The AI can see all scenarios in any team within the specified organization.

Team level

https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse?teamId=<id>

The AI can see all scenarios within the specified team.

Scenario level

https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse?scenarioId=<id>

The AI can only see the specified scenario.

This article outlines how to integrate the cloud-based Make MCP server with Claude Desktop.

Prerequisites

• NodeJS

• Claude Desktop app

• Make MCP Token

Installation

To use the cloud-based server with Claude Desktop:

1. Open your Claude Desktop account.

2. Click on the hamburger menu in the upper left-hand corner.

3. Click File.

4. Click Settings, which opens a dialog box.

5. Navigate to the Developer section.

6. Click Edit Config, which takes you to the folder containing the claude_desktop_config.json file.

1. Add the following configuration to the mcpServers section of your claude_desktop_config.json. Use the SSE endpoint with the token embedded directly in the URL:

https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse

Configuration example:

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse"
      ]
    }
  }
}

1. Replace <MAKE_ZONE> and <MCP_TOKEN> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MCP_TOKEN - You can generate your MCP token in your Make profile.

This article outlines how to integrate the cloud-based Make MCP server with Cursor.

Prerequisites

• Cursor app

Installation

To use the cloud-based server with Cursor:

1. Open your Cursor account.

2. On the upper right-hand side, click the gear icon to open the Cursor Settings dialog.

3. In the left sidebar, click Tools & Integrations.

4. Under MCP Tools, click New MCP Server to open the editor for the mcp.json file.

1. Use the SSE endpoint with the token embedded in the URL:

Configuration example:

1. Replace <MAKE_ZONE> and <MCP_TOKEN> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MCP_TOKEN - You can generate your MCP token in your Make profile.

This article outlines how to integrate the cloud-based Make MCP server with Vapi.

Prerequisites

• Vapi account

• MCP token

Installation

To add Make MCP server to Vapi:

1. Open your Vapi account.

2. Navigate to Tools on the left sidebar.

3. Click the Create Tool button, then select MCP.

4. Configure the tool name and describe when to use the tool.

5. In Server URL, add the following endpoint:

https://<MAKE_ZONE>/mcp/api/v1/u/<MCP_TOKEN>/sse

1. Replace <MAKE_ZONE> and <MCP_TOKEN> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MCP_TOKEN - You can generate your MCP token in your Make profile.

Optionally, to control tool access with more granularity, you can further configure the URL according to the levels outlined in Tool Access Control.

1. In Timeout, enter an appropriate timeout for your use case.

2. In MCP Settings, select Server-Sent Events (SSE).

3. Click Save.

You have now added Make MCP server to Vapi.

The local version of Make MCP server runs on your machine. You should only use it for advanced cases; in most other cases, use Cloud MCP Server instead.

Features

• Connects to your Make account to identify all scenarios scheduled On demand

• Parses scenario input and outputs (if defined) to enable AI systems to use scenarios effectively

• Facilitates scenario calling while validating all parameters

Prerequisites

• Make API key with scenarios:read and scenarios:run scopes

• At least one available Make scenario scheduled On demand

• MCP-compatible client (e.g., Claude Desktop app)

Installation and usage

1. Add the following configuration to the mcpServers section in your MCP client's configuration file (e.g., claude_desktop_config.json for Claude Desktop):

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": ["-y", "@makehq/mcp-server"],
      "env": {
        "MAKE_API_KEY": "<your-api-key>",
        "MAKE_ZONE": "<your-zone>",
        "MAKE_TEAM": "<your-team-id>"
      }
    }
  }
}

1. Replace placeholders:

• MAKE_API_KEY- Generate from your Make.com profile

• MAKE_ZONE- Your Make organization zone (e.g., eu2.make.com)

• MAKE_TEAM- Obtain from your team's page URL on Make.com

This article outlines how to integrate the local Make MCP server with Cursor.

Prerequisites

• Cursor app

• Make MCP Token

Installation

To use the local server with Cursor:

1. Open your Cursor account.

2. On the upper right-hand side, click the gear icon to open the Cursor Settings dialog.

3. In the left sidebar, click Tools & Integrations.

4. Under MCP Tools, click New MCP Server to open the editor for the mcp.json file.

1. Add the following configuration to the mcpServers section of your mcp.json file:

{
    "mcpServers": {
        "make": {
            "command": "npx",
            "args": ["-y", "@makehq/mcp-server"],
            "env": {
                "MAKE_API_KEY": "<your-api-key>",
                "MAKE_ZONE": "<your-zone>",
                "MAKE_TEAM": "<your-team-id>"
            }
        }
    }
}

1. Replace placeholders:

MAKE_API_KEY - You can generate an API key in your Make profile.

MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

MAKE_TEAM - The ID in the URL of the Team page.

This article outlines how to integrate the cloud-based Make MCP server with OpenAI API.

Prerequisites

• Make MCP Token

Installation

To use the cloud-based server with OpenAI API:

1. Configure your API call as follows:

curl https://api.openai.com/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{
  "model": "gpt-4.1",
  "input": "List all available tools.",
  "tools": [
    {
      "type": "mcp",
      "server_label": "make",
      "server_url": "https://<MAKE_ZONE>/mcp/api/v1/sse",
      }
    ]
  }'

1. Replace <MAKE_ZONE> and <MCP_TOKEN> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MCP_TOKEN - You can generate your MCP token in your Make profile.

This article outlines how to integrate the cloud-based Make MCP server with OpenAI.

Prerequisites

• OpenAI Platform account

• Make MCP Token

Installation

To add Make MCP server to OpenAI:

1. In OpenAI's Playground, sign in to your OpenAI account.

2. Navigate to Prompts.

3. In Tools, click the + button.

4. Select MCP Server.

5. In the dialog, click Add new to display the form below.

1. In URL, add this endpoint:

https://<MAKE_ZONE>/mcp/api/v1/u/sse

1. Replace <MAKE_ZONE> with your actual values.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

1. In Label, name your Make MCP server.

2. In Authentication, select Access token / API key.

3. Add your MCP token to the field that requires an access token.

4. Click Connect.

You have now added Make MCP server to OpenAI.

This article outlines how to integrate the local Make MCP server with Claude Desktop.

Prerequisites

• NodeJS

• Claude Desktop app

• Make API Key with scenarios:read andscenarios:run scopes

Installation

To use the local MCP server with Claude Desktop:

1. Open your Claude Desktop account.

2. Click on the hamburger menu in the upper left-hand corner.

3. Click File.

4. Click Settings, which opens a dialog.

5. Navigate to the Developer section.

6. Click Edit Config, which directs you to the folder containing the claude_desktop_config.json file.

1. Add the following configuration to the mcpServers section of your claude_desktop_config.json:

{
    "mcpServers": {
        "make": {
            "command": "npx",
            "args": ["-y", "@makehq/mcp-server"],
            "env": {
                "MAKE_API_KEY": "<your-api-key>",
                "MAKE_ZONE": "<your-zone>",
                "MAKE_TEAM": "<your-team-id>"
            }
        }
    }
}

1. Replace placeholders:

• MAKE_API_KEY - You can generate an API key in your Make profile.

• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).

• MAKE_TEAM - The ID in the URL of the Team page.