make-mcp-reference

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Make MCP Server Reference

Make MCP Server 参考文档

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

Make.com MCP服务器的技术参考文档——支持AI客户端执行场景并管理Make账户。

Connection Methods

连接方式

Codex Quick Setup

Codex 快速设置

If the Codex plugin installs but the Make MCP server is not present in

codex mcp list

, add it manually:

bash

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.

如果Codex插件已安装，但

codex mcp list

中未显示Make MCP服务器，请手动添加：

bash

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

登录后，在测试工具前重新连接Codex会话或开启新会话。

OAuth (Default)

OAuth（默认方式）

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

Endpoint:

https://mcp.make.com

URL variants:

Transport	URL
Stateless Streamable HTTP (default)	`https://mcp.make.com`
Streamable HTTP	`https://mcp.make.com/stream`
SSE	`https://mcp.make.com/sse`

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:

json

{
  "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.

通过OAuth授权流程连接。认证期间选择组织和权限范围。

端点：

https://mcp.make.com

URL变体：

传输方式	URL
无状态可流式HTTP（默认）	`https://mcp.make.com`
可流式HTTP	`https://mcp.make.com/stream`
SSE	`https://mcp.make.com/sse`

对于不支持SSE的客户端，可使用Cloudflare

mcp-remote

代理包装的旧版传输方式：

npx -y mcp-remote https://mcp.make.com/sse

。

Claude Code配置：

json

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

访问控制： 在OAuth授权期间限制特定组织。Teams及以上套餐支持团队级别的限制。

MCP Token

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

Endpoint:

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

URL variants:

Transport	URL
Stateless Streamable HTTP	`https://<ZONE>/mcp/u/<TOKEN>/stateless`
Streamable HTTP	`https://<ZONE>/mcp/u/<TOKEN>/stream`
SSE	`https://<ZONE>/mcp/u/<TOKEN>/sse`
Header Auth	`https://<ZONE>/mcp/stateless` + `Authorization: Bearer <TOKEN>`

Configuration for Claude Code:

json

{
  "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.

在Make个人资料→API访问标签页→添加令牌，生成令牌。

端点：

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

URL变体：

传输方式	URL
无状态可流式HTTP	`https://<ZONE>/mcp/u/<TOKEN>/stateless`
可流式HTTP	`https://<ZONE>/mcp/u/<TOKEN>/stream`
SSE	`https://<ZONE>/mcp/u/<TOKEN>/sse`
头部认证	`https://<ZONE>/mcp/stateless` + `Authorization: Bearer <TOKEN>`

Claude Code配置：

json

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

将

<MAKE_ZONE>

替换为组织的托管区域（例如

eu1.make.com

、

eu2.make.com

、

us1.make.com

）。

安全注意： 请将MCP令牌视为机密信息，切勿提交到版本控制系统中。

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

允许AI客户端查看并运行激活的按需场景。

OAuth权限范围： "Run your scenarios"
令牌权限范围：
```
mcp:use
```
适用套餐： 所有套餐

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

允许AI客户端查看并修改账户内容（场景、连接、Webhook、数据存储、团队）。

适用套餐： 仅付费套餐
支持对Make账户管理进行精细化控制

Configuring Scenarios as MCP Tools

将场景配置为MCP工具

For a scenario to appear as an MCP tool:

Set scenario to active status
Set scheduling to on-demand
Select the appropriate scope (
```
mcp:use
```
for tokens, "Run your scenarios" for OAuth)
Configure scenario inputs — these become tool parameters
Configure scenario outputs — these become tool return values
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

要让场景显示为MCP工具，需完成以下步骤：

将场景设置为激活状态
将调度设置为按需
选择合适的权限范围（令牌使用
```
mcp:use
```
，OAuth使用「Run your scenarios」）
配置场景输入——这些将成为工具参数
配置场景输出——这些将成为工具返回值
添加详细的场景描述——强烈建议添加，以帮助AI理解工具用途并提升可发现性

输入/输出最佳实践：

编写清晰、描述性的名称（AI Agent依赖这些信息）
添加详细描述说明预期数据
使用特定数据类型而非
```
Any
```
确保执行时间在超时限制内

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.

通过URL查询参数限制可用场景：

组织级别：

?organizationId=<id>

团队级别：

?teamId=<id>

场景级别（单个）：

?scenarioId=<id>

多个场景：

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

各级别互斥——无法同时组合组织、团队和场景过滤器。

Timeouts

超时设置

Tool Type	OAuth	Token (Stateless)	Token (SSE/Stream)
Scenario Run	25s	40s	40s
Management	30s	60s	320s

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.

工具类型	OAuth	令牌（无状态）	令牌（SSE/流式）
场景运行	25s	40s	40s
管理操作	30s	60s	320s

当场景运行超过超时时间时，响应会包含一个

executionId

。场景会在Make中继续运行最长40分钟。使用该ID调用

executions_get

接口轮询获取结果。

Advanced Configuration

高级配置

Tool Name Length

工具名称长度

Customize maximum tool name length with query parameter:

?maxToolNameLength=<32-160>

Default: 56 characters.

通过查询参数自定义工具名称的最大长度：

?maxToolNameLength=<32-160>

默认值：56字符。

Troubleshooting

故障排查

Issue	Solution
Scenario not appearing as tool	Verify: active status, on-demand scheduling, correct scope
Timeout errors	Switch from `https://mcp.make.com` to a zone-specific `https://<MAKE_ZONE>/mcp/<TRANSPORT>` URL for longer timeouts. Alternatively, reduce scenario complexity or use SSE transport
Permission denied	Check token scopes and access control parameters
Connection refused	Verify zone URL and token validity
Stale tool list	Reconnect MCP client to refresh available tools

问题	解决方案
场景未显示为工具	验证：激活状态、按需调度、正确的权限范围
超时错误	将 `https://mcp.make.com` 切换为区域特定的 `https://<MAKE_ZONE>/mcp/<TRANSPORT>` URL以获得更长超时时间。或者，降低场景复杂度或使用SSE传输方式
权限拒绝	检查令牌权限范围和访问控制参数
连接被拒绝	验证区域URL和令牌有效性
工具列表过时	重新连接MCP客户端以刷新可用工具

Resources

参考资源

references/transport-details.md
— Detailed transport comparison, URL construction, and zone list
Make MCP Server docs — 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

references/transport-details.md
— 详细的传输方式对比、URL构建及区域列表
Make MCP Server 官方文档 — 官方文档
make-scenario-building 技能 — 场景构建：路由、过滤、迭代、聚合、错误处理、蓝图构建
make-module-configuring 技能 — 模块配置：参数、连接、映射、Webhook、数据存储