Make MCP Server

Make MCP server

Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage your Make account. Model Context Protocol (MCP) is a communication standard between AI and external systems that enables safe interactions by defining endpoints and providing authentication.

How Make MCP server works

AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server gives them access to MCP tools that:

• Run active and on-demand scenarios.

• View and modify scenarios and their related entities, such as connections, webhooks, and data stores.

• View and modify teams and organizations.

Scopes determine the . Scenario run tools are available to all plans, and management tools are available to paid plans. You select scopes when you .

Make Skills are Markdown files with instructions on building scenarios, configuring modules, and connecting to Make MCP server or third-party services.

You can install them in MCP clients to connect to Make MCP server without setting up the connection manually and help clients reliably perform Make-specific tasks.

For installation instructions, see .

Make MCP server is a Make-hosted, cloud-based server that runs via stateless Streamable HTTP.

Connect it to MCP clients using OAuth or an MCP token. Alternatively, install Make Skills, which include connection details for Make MCP server.

Use the following connection URL:

For more information, see .

The URL you use depends on whether your client supports adding the MCP token in Authorization headers.

MCP token in URL

Use the following connection URL, and replace <MAKE_ZONE> and <MCP_TOKEN> with actual values:

• MAKE_ZONE: The zone your organization is hosted in. For example, eu2.make.com.

• MCP_TOKEN: Your MCP token. To obtain one, see .

Optionally, append the following query parameter to the URL to set the tool name length:

• ?maxToolNameLength=<length>: Generated tool names have a maximum length of 56 characters by default, to be compatible with most AI systems. Use this parameter to set a different maximum length. The allowed range is 32 to 160 characters.

MCP token in header

If you add the MCP token in an Authorization header, use the following URL:

Specify the MCP token in the Authorization header:

MCP tools are functions on Make MCP server that MCP clients call to interact with Make, such as running scenarios or updating data stores.

You can view the tools on Make MCP server in a few ways:

Tool calls from MCP clients to Make MCP server have a timeout for returning output. Limits depend on the tool type and connection method.

Scenario run tools

• https://mcp.make.com (OAuth): 25 seconds

• https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN> (MCP token): 40 seconds

Management tools

• https://mcp.make.com (OAuth): 30 seconds

• https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN> (MCP token): 60 seconds

Retrieve outputs after timeout

If a scenario run tool call times out, the scenario continues running in Make for up to 40 minutes. The timeout response includes an executionId that an MCP client can use to get the output after the scenario finishes.

Example response:

Select the scenarios:read scope to allow an MCP client to retrieve outputs after a timeout once a scenario run finishes.

When an MCP client uses a scenario as a tool, it refers to the scenario's to know what data to send and what it gets back:

• Inputs are parameters that an MCP client fills with data when the scenario runs.

• Outputs are data the scenario returns to the MCP client.