# Make Cloud MCP Server

{% hint style="info" %}
This page is outdated; refer to [Make MCP Server ](https://developers.make.com/mcp-server/make-mcp-server)for the latest information. 
{% endhint %}

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 
* 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:

```json
{
  "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.

{% hint style="warning" %}
To control which tools are visible to your AI, you can follow the [Tool Access Controls](https://developers.make.com/mcp-server/connect-using-mcp-token/scenarios-as-tools-access-control) guide.
{% endhint %}

#### 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](https://blog.cloudflare.com/remote-model-context-protocol-servers-mcp/#connect-to-remote-mcp-servers-from-mcp-clients-that-today-only-support-local-mcp) for more details.

Configuration example:

```json
{
  "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.

{% hint style="warning" %}
To control which tools are visible to your AI with more granularity, you can follow the [Tool Access Controls](https://developers.make.com/mcp-server/connect-using-mcp-token/scenarios-as-tools-access-control) guide.
{% endhint %}

## 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.