> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/mcp-server/make-cloud-mcp-server.md).

# 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.md)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 API key
* 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/<API_KEY>/sse
```

Configuration example:

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

Replace `<MAKE_ZONE>` and `<API_KEY>` with your actual values.

* `MAKE_ZONE` - The zone your organization is hosted in (e.g., `eu2.make.com`).
* `API_KEY` - Your API key for MCP.

{% 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-api-key/scenarios-as-tools-access-control.md) 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 API key in the Authorization header as follows:

```
Authorization: Bearer <API_KEY>
```

### 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/<API_KEY>/sse"
      ]
    }
  }
}
```

Replace `<MAKE_ZONE>` and `<API_KEY>` with your actual values.

* `MAKE_ZONE` - The zone your organization is hosted in (e.g., `eu2.make.com`).
* `API_KEY` - Your API key for MCP.

{% 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-api-key/scenarios-as-tools-access-control.md) 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.make.com/mcp-server/make-cloud-mcp-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
