Make MCP Server

Make MCP server allows external AI systems, such as AI agents, to run your scenarios and manage the contents of your Make account. Model Context Protocol (MCP) is a communication standard between AI systems and external systems. It enables them to easily and safely interact by defining endpoints and providing authentication.

Benefits

• Creates bidirectional communication between AI and Make

• Allows AI to access and manage elements of your Make account

• Turns your active and on-demand scenarios into callable tools for AI

How does Make MCP server work?

Make MCP server gives external AI systems access to scenario run and management tools that enable the following capabilities:

• Run active and on-demand scenarios

• View and modify scenarios and their related entities (e.g., connections, webhooks, and data stores)

• View and modify teams and organizations

When connecting Make MCP server to an AI system, you select the scopes to determine the tools available to the system.

When connecting to Make MCP server, note that the use of scenarios as tools is available to all plans, and management tools are available to paid plans.

Inputs and outputs

If you're using scenarios as tools, you can help AI understand what data to receive and send 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

We strongly recommend adding detailed scenario descriptions. These help your AI understand the purpose of the scenario and improve the reliability of your prompts.

Available transport methods

Make MCP server is a cloud-based server hosted by Make, running via Server-Sent Events (SSE) and Streamable HTTP.

Clients with SSE support

If your MCP client supports SSE, use the following connection URLs, depending on your connection type:

OAuth

https://mcp.make.com/sse

MCP token

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

In the above configuration, 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 control which scenarios are available as tools through your MCP token, see Scenarios as tools access control.

Optionally, you can append the following advanced query parameters to the 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.

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

If your MCP client does not support SSE, use the Cloudflare mcp-remote proxy for compatibility. Refer to Cloudflare's MCP Remote Proxy Guide for more details.

OAuth

Configuration example:

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.make.com/sse"
      ]
    }
  }
}

MCP token

Configuration example:

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

Clients with Streamable HTTP support

If your MCP client supports Streamable HTTP, use /stream instead of /sse at the end of the connection URL specified for your chosen connection type (OAuth or MCP token).