Make Cloud MCP Server
Last updated
Last updated
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.
Make MCP Token ()
At least one available Make scenario with "On Demand" scheduling
MCP-compatible client (e.g., Cursor App or Claude Desktop App).
If your client supports SSE, use the following endpoint:
Configuration example:
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.
If your client supports sending authorization in HTTP headers, you can use the following URL:
With the MCP token specified in the Authorization header as follows:
Configuration example:
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.
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.
To control which tools are visible to your AI with more granularity, you can follow the guide.
Use the Cloudflare mcp-remote
proxy for compatibility. Refer to for more details.
To control which tools are visible to your AI with more granularity, you can follow the guide.