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:
https://mcp.make.com
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 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).
Usage with Cursor
This guide outlines how to connect Make MCP server to Cursor using OAuth.
Prerequisites
Cursor account (Desktop version)
Connect to Cursor
To connect Make MCP server to Cursor:
Open your Cursor account.
On the upper right-hand side, click the gear icon to open the Cursor Settings dialog.
In the left sidebar, click Tools & Integrations (or Tools, if you're on the Free Plan).
In the editor, add the configuration.
Use the following URL:
Configuration example:
If you experience connection issues, you can add /stateless or /stream to the end of your connection URL. For SSE, add /sse instead.
In MCP Tools, you'll see Make added as an MCP tool. Click Needs login.
In the dialog, click Open, which opens an OAuth consent screen.
In the Organization dropdown, select the organization that can access the server.
Select its granted scopes.
You have now connected Make MCP server to Cursor.
Under MCP Tools, click Add Custom MCP to open the editor for the mcp.json file.
Click Allow, then Open Cursor.
Click Open to allow the extension to open the URI.
In Windsurf, click the Settings icon in the top-right corner, and select Windsurf Settings.
In Cascade, click the Open MCP Marketplace link next to MCP Servers.
In Installed MCPs, click the Settings icon to open the mcp.config.json configuration file.
If you experience connection issues, you can add /stateless or /stream to the end of the connection URL.
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.
You have now connected Make MCP server to Windsurf.
Call tools on Windsurf
You can call Make MCP tools in the chat:
Click the Toggle Cascade Side Bar icon in the top-right corner, or enter Ctrl+Alt+B (Windows) or Cmd+Option+B (Mac).
Enter a question related to your connected Make MCP tools.
Windsurf calls the relevant tool and responds to your question.
Usage with OpenAI
This guide outlines how to connect Make MCP server to OpenAI using an MCP token.
Prerequisites
OpenAI Platform account
Connect to OpenAI
To connect Make MCP server to OpenAI:
In OpenAI's Playground, sign in to your OpenAI account.
Navigate to Prompts.
In Tools, click the + button.
In URL, add the following URL:
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
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.
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
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.
Usage with Vapi
This guide outlines how to connect Make MCP server to Vapi.
Prerequisites
Vapi account
Usage with Cursor
This guide outlines how to connect Make MCP server to Cursor using an MCP token.
Prerequisites
Cursor account (Desktop version)
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
Usage with Warp
This guide outlines how to connect Make MCP server to Warp using OAuth.
Prerequisites
Usage with Claude
This guide outlines how to connect Make MCP server to Claude using OAuth.
Prerequisites
Claude account
Scenario
Scenarios must be active with on-demand scheduling to be discoverable as MCP tools.
The following applies only to scenario tools, and excludes management tools and other tool types.
Configure the tool name and describe when to use the tool.
In Server URL, add the following URL:
If you experience connection issues, you can add /stream instead of /stateless to the end of your connection URL. For SSE, add /sse instead.
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.
Optionally, to control which scenarios are available as tools, you can further configure the URL according to the levels outlined in scenarios as tools access control.
In Timeout, enter an appropriate timeout for your use case.
In MCP Settings, select Streamable HTTP or Server-Sent Events (SSE).
Click Save.
You've now connected Make MCP server to Vapi.
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.
Turns your active and on-demand scenarios into callable tools for AI
How Make MCP server works
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 run (Run your scenarios) toolsare available to all plans, and management (View and modify...) tools are available to paid plans.
Scenario inputs and outputs
When using scenarios as MCP tools, define scenario inputs and outputs to 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
Detailed scenario descriptions are strongly recommended. They 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 Streamable HTTP and Server-Sent Events (SSE).
Clients with Stateless Streamable HTTP support
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:
OAuth
https://mcp.make.com
MCP token
https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN>/stateless
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 .
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:
Clients with Streamable HTTP support
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).
Clients with Server-Sent Events (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/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 .
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:
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.
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:
Select the scenarios:read scope to enable MCP clients to retrieve outputs after timeout once a scenario run finishes.
Management tool timeout limits
https://mcp.make.com (OAuth): 30 seconds
https://<MAKE_ZONE>/mcp/<TRANSPORT> (MCP token, direct OAuth):
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.
{
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,
},
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).
An MCP token is a secret key. Treat it as sensitive information and share it only with trusted parties.
