Make Mcp Reference

Make MCP Server Reference

Technical reference for the Make.com MCP server — enables AI clients to execute scenarios and manage Make accounts.

Known Make module id: the Make Code module is "module": "code:ExecuteCode".

Connection Methods

Codex Quick Setup

If the Codex plugin installs but the Make MCP server is not present in codex mcp list, add it manually:

codex mcp add make --url https://mcp.make.com
codex mcp login make

After login, reconnect the Codex session or start a new one before testing tools.

OAuth (Default)

Connect via OAuth consent flow. Select organization and scopes during authentication.

Endpoint: https://mcp.make.com

URL variants:

For clients without SSE support, a legacy transport using the Cloudflare mcp-remote proxy wrapper is available: npx -y mcp-remote https://mcp.make.com/sse.

Configuration for Claude Code:

{
  "mcpServers": {
    "make": {
      "type": "http",
      "url": "https://mcp.make.com"
    }
  }
}

Access control: Restrict to specific organizations during OAuth consent. Teams plan or higher enables team-level restrictions.

MCP Token

Generate a token in Make profile → API access tab → Add token.

Endpoint: https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN>/stateless

URL variants:

Configuration for Claude Code:

{
  "mcpServers": {
    "make": {
      "type": "http",
      "url": "https://<MAKE_ZONE>/mcp/u/<MCP_TOKEN>"
    }
  }
}

Replace <MAKE_ZONE> with the organization's hosting zone (e.g., eu1.make.com, eu2.make.com, us1.make.com).

Security: Treat MCP tokens as secrets. Never commit them to version control.

Scopes

Scenario Run Scopes

Allow AI clients to view and run active, on-demand scenarios.

• OAuth scope: "Run your scenarios"
• Token scope: mcp:use
• Available on: All plans

Management Scopes

Allow AI clients to view and modify account contents (scenarios, connections, webhooks, data stores, teams).

• Available on: Paid plans only
• Enable granular control over Make account management

Configuring Scenarios as MCP Tools

For a scenario to appear as an MCP tool:

1. Set scenario to active status 2. Set scheduling to on-demand 3. Select the appropriate scope (mcp:use for tokens, "Run your scenarios" for OAuth) 4. Configure scenario inputs — these become tool parameters 5. Configure scenario outputs — these become tool return values 6. Add a detailed scenario description — strongly recommended to help AI understand the tool's purpose and improve discoverability

Input/output best practices:

• Write clear, descriptive names (AI agents rely on these)
• Add detailed descriptions explaining expected data
• Use specific data types over Any
• Keep execution time under timeout limits

Access Control (Token Auth)

Restrict which scenarios are available via URL query parameters:

Organization level:

?organizationId=<id>

Team level:

?teamId=<id>

Scenario level (single):

?scenarioId=<id>

Multiple scenarios:

?scenarioId[]=<id1>&scenarioId[]=<id2>

Levels are mutually exclusive — cannot combine organization, team, and scenario filters.

Timeouts

When a scenario run exceeds the timeout, the response includes an executionId. The scenario continues running in Make for up to 40 minutes. Use executions_get with that ID to poll for results.

Advanced Configuration

Tool Name Length

Customize maximum tool name length with query parameter:

?maxToolNameLength=<32-160>

Default: 56 characters.

Troubleshooting

Resources

• `references/transport-details.md` — Detailed transport comparison, URL construction, and zone list
• [Make MCP Server docs](https://developers.make.com/mcp-server) — Official documentation
• make-scenario-building skill — Scenario construction: routing, filtering, iterations, aggregations, error handling, blueprint construction
• make-module-configuring skill — Module configuration: parameters, connections, mapping, webhooks, data stores

Make MCP Server Transport Details

Transport Methods Comparison

Stateless Streamable HTTP (Default)

• Each request is independent — no session state
• Best for simple tool calls and management operations
• Fastest for single operations
• Default transport when no suffix is specified

When to use: Most use cases, especially quick scenario executions and management queries.

Streamable HTTP

• Maintains streaming connection for longer operations
• Supports real-time progress updates
• Better for operations that may take longer than a few seconds

When to use: Long-running scenarios, operations where progress feedback is valuable.

Server-Sent Events (SSE)

• Persistent connection with server-push capability
• Longest timeout limits (320s for token-based management tools)
• Best for management operations that may take extended time

When to use: Extended management operations, clients that require SSE transport.

URL Construction

Base URL Pattern

OAuth: https://mcp.make.com[/suffix] Token (path): https://<ZONE>/mcp/u/<TOKEN>[/suffix] Token (header): https://<ZONE>/mcp[/suffix] + Authorization: Bearer <TOKEN>

Suffixes

Query Parameters

Append to any URL:

• ?organizationId=<id> — restrict to organization
• ?teamId=<id> — restrict to team
• ?scenarioId=<id> — restrict to scenario
• ?scenarioId[]=<id1>&scenarioId[]=<id2> — multiple scenarios
• ?maxToolNameLength=<32-160> — tool name length

The access control parameters (organizationId, teamId, scenarioId) apply only to scenario run tools and do not restrict management tools. The maxToolNameLength parameter applies to all tools.

Complete URL Examples

OAuth SSE with tool name config:

https://mcp.make.com/sse?maxToolNameLength=100

Token stateless with org restriction:

https://eu2.make.com/mcp/u/abc123/stateless?organizationId=456

Token SSE with multiple scenarios:

https://us1.make.com/mcp/u/abc123/sse?scenarioId[]=1&scenarioId[]=2

Header auth with team restriction:

https://eu1.make.com/mcp/sse?teamId=789
Authorization: Bearer abc123

Make Zones

Example hosting zones:

• eu1.make.com — Europe 1
• eu2.make.com — Europe 2
• us1.make.com — United States 1
• us2.make.com — United States 2
• eu1.make.celonis.com — Enterprise Europe 1
• us1.make.celonis.com — Enterprise United States 1

There are more zones available beyond these examples. Find your zone in Make account settings or from the URL when logged into Make.

Official Documentation

• MCP Server
• Connect Using OAuth
• Connect Using MCP Token