By default, your MCP token grants access to all your tools across every organization you belong to. To restrict the tools your AI systems can access, you can append specific query parameters to the MCP URL address.

Organization-level

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

The Agent will see all scenarios within any team under the specified organization.

Team-level

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

The Agent will see all scenarios within the specified team.

Scenario-level

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

The Agent will only see the specified scenario.

Prerequisites

• NodeJS

• Claude Desktop App

• Make MCP token

Installation

To use this server with the Claude Desktop app, open the Settings dialog and navigate to the Developer section. By clicking Edit Config, you’ll be directed to the folder containing the claude_desktop_config.json file.

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"
      ]
    }
  }
}

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.

To obtain the MCP Token, navigate to the API / MCP access section in your Make user profile. Click Add token and select MCP Token as the type. Choose a label for your MCP Token and click Add.

Make MCP server enable seamless integration of Make scenarios into AI systems such as AI Assistants and Agents, empowering them to perform real-world tasks through your pre-configured workflows.

Benefits

• Turn your Make scenarios into callable tools for your AI

• Maintain complex automation logic in Make while exposing functionality to your AI

• Create bidirectional communication between your AI and your existing automation workflows

How does it work?

Make MCP Server lists all your scenarios scheduled to run "On Demand" as tools available to your AI. Each scenario can be configured with:

• Inputs: parameters that your AI will fill with data when the scenario runs

• Outputs: data that will be returned from the scenario back to your AI

Make MCP Servers

We currently allow two possible ways how to integrate Make MCP server:

Cloud-based MCP Server, hosted by Make, that runs via SSE (Server-Sent Events), suitable for any integrations and environments.

Basic MCP server version that you are able to run locally on your machine, ideal for scenarios that require local management and control and also when you know what you are doing.

Features

• Allows integration with Make scenarios through SSE endpoints.

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

• Supports scenarios execution remotely via Make infrastructure.

Prerequisites

• At least one available Make scenario with "On Demand" scheduling

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

Installation and Usage

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

With the MCP token specified in the Authorization header as follows:

Authorization: Bearer <MCP_TOKEN>

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

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.

Advanced Parameters

Additionally, you can append the following advanced query parameters to the MCP URL for an even more customized experience.

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

Prerequisites

• Cursor App

• Make MCP Token

Installation

To use this server with the Cursor app, open the Cursor Settings dialog and navigate to the MCP section. By clicking Add new global MCP server you’ll open an editor for the mcp.json file.

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": {
      "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.

Prerequisites

• NodeJS

• Claude Desktop App

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

Installation

To use this server with the Claude Desktop app, open the Settings dialog and navigate to the Developer section. By clicking Edit Config, you’ll be directed to the folder containing the claude_desktop_config.json file.

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

• 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 - You can find the ID in the URL of the Team page.

Features

• Connects to your Make account to identify all "On Demand" scenarios.

• Automatically parses scenario input parameters, enabling AI assistants to understand and utilize scenarios effectively.

• Facilitates scenario invocation with validated parameters.

• Returns structured JSON output from scenarios (currently available in closed beta).

Prerequisites

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

• At least one available Make scenario with "On Demand" scheduling

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

Installation and Usage

Add the following configuration to the mcpServers section in your MCP client's configuration file (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>"
      }
    }
  }
}

Replace placeholders:

• MAKE_API_KEY: Generate from your Make.com profile.

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

• MAKE_TEAM: Obtainable from your team's page URL on Make.com.