The MCP server is included with Make and does not cost extra to connect; running scenarios consumes Make operations on your plan, including the free tier's monthly allowance. Usage of each connected app follows your own Make connections.

Does it support remote/OAuth?

It is a hosted remote server over streamable HTTP and SSE. Authentication is a Make MCP token (with the mcp:use scope) that you either embed in the zone-specific connection URL or send as a Bearer Authorization header — there is no separate OAuth flow for the MCP connection itself.

Make MCP server

OfficialMake (Celonis)Config last verified Jun 1, 2026

Make's official cloud MCP server: turn your Make scenarios into callable tools so an agent can run multi-step automations on demand.

The Make MCP server is Make's official cloud integration that exposes your Make scenarios to an AI agent as tools. Make (formerly Integromat) is a visual automation platform where you build scenarios that connect apps and APIs across thousands of integrations. This server turns any scenario you flag as on-demand into a tool the agent can call: it tells the AI which scenarios are available, what inputs each one needs, and what outputs it returns, so the agent can trigger a real automation — enrich a lead, post to multiple channels, sync records — and use the structured result in its next step.

It is a fully hosted cloud server, so there is nothing to install or run yourself. You connect over streamable HTTP or SSE using a Make MCP token that you generate in your Make profile with the mcp:use scope. The connection URL is zone-specific and embeds the token, following the pattern https://<zone>.make.com/mcp/api/v1/u/<MCP_TOKEN>/sse (for example eu2.make.com or a US zone), or you can send the token as a Bearer Authorization header against the header-based endpoint. A convenience host at https://mcp.make.com is also available; if you hit timeouts on long-running scenarios, switch to the zone-specific URL for longer timeouts. Because the tool surface is generated from your own scenarios, the available tools are exactly the automations you choose to expose — there is no fixed built-in tool list.

Quick install

Copy-paste configs are provided for all 8 supported clients. Pick your client below.

Add to ~/.claude.json

~/.claude.json

json

{
  "mcpServers": {
    "make": {
      "type": "http",
      "url": "https://mcp.make.com/mcp/api/v1/sse",
      "headers": {
        "Authorization": "Bearer <MAKE_MCP_TOKEN>"
      }
    }
  }
}

Or via CLI

bash

claude mcp add --transport http make https://mcp.make.com/mcp/api/v1/sse

Step-by-step guides

Required configuration

MAKE_MCP_TOKENRequired
Make MCP token generated in your Make profile with the mcp:use scope. Sent as a Bearer Authorization header, or embedded in a zone-specific URL like https://<zone>.make.com/mcp/api/v1/u/<MCP_TOKEN>/sse. Required.

What you can do with it

Trigger Make automations from your agent

Expose a scenario such as 'enrich and route a new lead' as a tool. The agent calls it with the required inputs, Make runs the multi-step automation across your connected apps, and the agent receives the structured output to continue its work.

Control which automations the AI can run

Only the scenarios you mark as available become tools, and your MCP token's scopes gate access. This lets you give an agent a curated, auditable set of real-world actions instead of broad, unscoped API access.

FAQ

Is it free?: The MCP server is included with Make and does not cost extra to connect; running scenarios consumes Make operations on your plan, including the free tier's monthly allowance. Usage of each connected app follows your own Make connections.
Does it support remote/OAuth?: It is a hosted remote server over streamable HTTP and SSE. Authentication is a Make MCP token (with the mcp:use scope) that you either embed in the zone-specific connection URL or send as a Bearer Authorization header — there is no separate OAuth flow for the MCP connection itself.

← Browse all automation servers