You can connect Make MCP server to MCP clients using OAuth.
OAuth is recommended due to its simple and secure setup, with a universal URL that eliminates the need to configure the URL with an MCP token.
Connection URL
To connect Make MCP server using OAuth, use this URL for Stateless HTTP Streamable:
If you experience connection issues, you can add /stateless or /stream to the end of the URL. If your client only supports SSE, add /sse instead.
Access control
While connecting Make MCP server with an MCP client, you will select the organization and granted scopes in the OAuth consent screen. Scopes determine the tools available to the MCP client.
Consent screen example:
The Run your scenarios scope provides access to all on-demand and active scenarios within a specific organization.
For more granular control, a Teams plan or higher allows you to limit scenario access to specific teams in your organization, as you can create user accounts that have access only to particular teams.
To complete the connection, refer to the Usage page of your MCP client (e.g., Usage with Cursor).
https://mcp.make.com
Make MCP Server
Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account. Model Context Protocol (MCP) is a communication standard between AI and external systems. It enables safe interactions 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
Usage with Claude
This guide outlines how to connect Make MCP server to Claude using OAuth.
Claude account
Make is a built-in connector on Claude. To connect Make MCP server to Claude:
Open your Claude account.
Usage with Claude Code
This guide outlines how to connect Make MCP server to Claude Code using OAuth.
To connect Make MCP server to Claude Code:
Usage with ChatGPT
This guide outlines how to connect Make MCP server to ChatGPT using OAuth.
ChatGPT account (paid subscription)
To connect Make MCP server to ChatGPT:
Open the web version of ChatGPT.
Usage with Kiro
This guide outlines how to connect Make MCP server to Kiro using OAuth.
To connect Make MCP server to Kiro:
In Kiro, click the ghost icon on the left sidebar.
Usage with Mistral AI
This guide outlines how to connect Make MCP server to Mistral AI's Le Chat using OAuth.
Mistral AI account
To connect Make MCP server to Mistral AI:
Open Mistral AI and go to Le Chat.
Usage with OpenAI API
This guide outlines how to connect Make MCP server to the OpenAI API.
To connect Make MCP server to the OpenAI API:
Configure your API call with the following:
Go to Customize on the left sidebar.
Click Connectors.
Click the + sign at the top, then Browse connectors.
Search for Make and click the + sign.
In the OAuth consent screen, select an organization in Organization and its scopes.
Click Allow to proceed.
You've now connected Make MCP server to Claude.
Prerequisites
Connect to Claude
Replace <MAKE_ZONE> with your actual values.
MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).
You've now connected Make MCP server to the OpenAI API.
Prerequisites
Connect to OpenAI API
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
claude mcp add --transport http make https://mcp.make.com
claude mcp add --transport sse make https://mcp.make.com/sse
https://mcp.make.com
Turns your active and on-demand scenarios into callable tools for AI
AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to scenario run and management tools that enable the following actions:
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 you connect Make MCP server to an MCP client, your selected scopes determine the callable tools available on the server.
Scenario inputs and outputs
When using scenarios as MCP tools, scenario inputs and outputs help AI understand what data to receive and send:
Inputs: parameters that AI fills with data when the scenario runs
Outputs: data returned from the scenario to your AI
It is highly recommended to install Make Skills in your AI assistant before using Make MCP server. Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modules, and connecting to Make MCP server or third-party services.
Make MCP server is a cloud-based server hosted by Make, running via Streamable HTTP and Server-Sent Events (SSE).
Stateless Streamable HTTP is Make's default transport method due to its connection reliability. It is recommended when connecting to MCP clients that support Streamable HTTP.
Use the following connection URLs, depending on your connection type:
If your MCP client supports Streamable HTTP, you can use /stream at the end of the connection URL specified for your chosen connection type (OAuth or MCP token).
If your MCP client supports SSE, use the following connection URLs, depending on your connection type:
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.
Calls from MCP clients to tools on Make MCP server have timeout limits for returning output. Timeouts vary depending on the tool type called and the authorization and transport method used.
Even after a scenario run tool call times out, the called scenario continues running in Make for up to 40 minutes, and you can retrieve the output after the scenario finishes its run.
The call returns a timeout response that includes the executionId , which the MCP client can use to retrieve the output, once ready, with the corresponding tool.
Example response:
https://mcp.make.com (OAuth): 30 seconds
https://<MAKE_ZONE>/mcp/<TRANSPORT> (MCP token, direct OAuth):
{
instruction: 'The Tool execution has started, but did not complete yet. Use a corresponding Tool for getting Execution Results to check for the result asynchronously.',
executionId: '4eb841b3fe3d48a5b2b59e2eed3f55be',
scenarioId: 1,
},
How Make MCP server works
Scenario run (Run your scenarios) toolsare available to all plans, and management (View and modify...) tools are available to paid plans.
Detailed scenario descriptions help your AI understand the purpose of the scenario and improve the reliability of your prompts.
Install Make Skills
Available transport methods
Clients with Stateless Streamable HTTP support
OAuth
MCP token
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).
Clients with Streamable HTTP support
Clients with Server-Sent Events (SSE) support
OAuth
MCP token
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).
Clients without SSE support
OAuth
Configuration example:
MCP token
Configuration example:
Timeouts for tool calls
Scenario run tool timeout limits
Select the scenarios:read scope to enable MCP clients to retrieve outputs after timeout once a scenario run finishes.
Management tool timeout limits
Management tool calls are typically fast and rarely time out. If you still experience timeouts when using https://mcp.make.com, switch to a https://<MAKE_ZONE>/mcp/<TRANSPORT> URL for longer timeouts.
Click on your profile name on the left sidebar.
Click Settings to open the settings dialog.
Go to Apps on the left sidebar, then click Advanced settings.
In Advanced settings, enable Developer mode.
Return to Apps, and click the Create app button that is now visible.
In the New App dialog, name your MCP server.
In Connection, add the following URL:
In Authentication, select OAuth.
Select I understand and want to continue.
Click Create.
In the OAuth consent screen, select your organization and its scopes.
Click Allow.
You have now connected Make MCP server to ChatGPT. In Apps, youcan view its details and select which tools ChatGPT can use.
Once you add Make MCP server, enable it in the chat:
Open a new chat in ChatGPT.
In the left-hand corner of the message bar, click the + sign to open a dropdown.
Click More, then select the Make MCP server that you connected before.
You have now enabled Make MCP server in the chat, allowing ChatGPT to use Make tools when interacting with you.
Prerequisites
Connect to ChatGPT
https://mcp.make.com
If you experience connection issues, you can add /stateless or /stream to the end of your connection URL. For SSE, add /sse instead.
Enable in chat
Hover over the MCP servers section and click the Open MCP Config icon.
In the mcp.json configuration, add the following:
Enter Ctrl + S (Windows) or Cmd + S (Mac) to save. The OAuth consent screen opens in a new browser window.
In the consent screen, select your organization and scopes, then click Allow.
Return to the MCP servers section to check whether Make MCP server connected successfully.
You have now connected Make MCP server to Kiro.
You can call Make MCP tools in the chat:
To open the chat, enter Ctrl + L (Windows) or Cmd + L (Mac).
Enter a question related to your connected Make MCP tools.
When asked for permission to call a specific MCP tool, click Accept.
Kiro calls the relevant tool and responds to your question.
In your terminal, run the following command, depending on your transport method:
Streamable HTTP
Server-Sent Events (SSE)
Run the Gemini command to start Gemini.
Run /mcp list to check if Make is among your configured MCP servers.
Run /mcp auth make to initiate authentication.
You have now connected Make MCP server to Gemini CLI.
You can call Make MCP tools in Gemini CLI:
Enter a question related to your connected Make MCP tools.
Grant permission for the suggested tool.
Gemini CLI calls the relevant tool and responds to your question.
Connect using MCP token
You can connect Make MCP server to a client using an MCP token in the connection URL. An MCP token is an API token that you create in Make for adding Make MCP server to an MCP client.
Obtain MCP token
To obtain an MCP token:
In the top-right corner of your Make account, click your name.
Click Profile.
Navigate to the API access tab.
In Tokens, click Add token, which opens a dialog.
Select your desired scopes, including the mcp:use scope if you want to make your scenarios available as tools.
In Label, name your API token.
Click Add.
You have now generated an MCP token for your MCP client. Include this token in the connection URL. To complete the connection, refer to the Usage page of your MCP client (e.g., Usage with Cursor).
To control which scenarios are available as tools through your MCP token, see .
Usage with Cursor
This guide outlines how to connect Make MCP server to Cursor using an MCP token.
In OpenAI's Playground, sign in to your OpenAI account.
Navigate to Prompts.
In Tools, click the + button.
Select MCP Server.
In the dialog, click Add new to display the form below.
In URL, add the following URL:
Replace <MAKE_ZONE> with your actual values.
MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).
In Label, name your Make MCP server.
In Authentication, select Access token / API key.
Add your MCP token to the field that requires an access token.
You've now connected Make MCP server to OpenAI.
Scenarios as tools access control
By default, the mcp:use scope of your MCP token allows AI systems to access all active and on-demand scenarios across all of your Make organizations. If you want to restrict access, append query parameters to the connection URL according to these levels:
Organization
Team
Scenario
Scenarios must be active with on-demand scheduling to be discoverable as MCP tools.
If you experience connection issues, you can add /stateless or /stream to the end of your connection URL. For SSE, add /sse instead.
Call tools on Warp
Return to the Installed MCPs section to check whether Make MCP server connected successfully.
If you experience connection issues, you can add /stateless or /stream to the end of the connection URL.
Call tools on Windsurf
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
In the OAuth consent screen, select your organization and scopes, then click Allow.
If you experience connection issues, you can add /stateless or /stream to the end of your connection URL.
Call tools on Gemini CLI
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
MCP tool calls from Vapi Assistants may exceed Make API rate limits, resulting in rate limit errors. Check your Make API rate limit, as defined in your plan, in Make API rate limits.
scenarios as tools access control
Click Connect.
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
Click Allow, then Open Cursor.
Click Open to allow the extension to open the URI.
If you experience connection issues, you can add /stateless or /stream to the end of your connection URL. For SSE, add /sse instead.
MCP_TOKEN - You can generate your MCP token in your Make profile.
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:
Specify the MCP token in the Authorization header as follows:
MCP_TOKEN - You can generate your MCP token in your Make profile.
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:
Specify the MCP token in the Authorization header as follows:
