原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Make MCP

作者:danishashko版本 1.3.3i★ –i在你的电脑上运行
注册名称io.github.danishashko/make-mcp

安装

概览

作者提供的说明(英文原文)

Unofficial MCP server for Make.com automation - build, validate & deploy scenarios via AI

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具
  • 你需要填写:MAKE_API_KEY

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: MAKE_API_KEY, MAKE_TEAM_ID, MAKE_API_URL, LOG_LEVEL

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "your-value",
        "MAKE_TEAM_ID": "your-value",
        "MAKE_API_URL": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add make --env MAKE_API_KEY=your-value --env MAKE_TEAM_ID=your-value --env MAKE_API_URL=your-value --env LOG_LEVEL=your-value -- npx -y make-mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "your-value",
        "MAKE_TEAM_ID": "your-value",
        "MAKE_API_URL": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "make": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "make-mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "your-value",
        "MAKE_TEAM_ID": "your-value",
        "MAKE_API_URL": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • MAKE_API_KEY 机密 env
    Make.com API key for scenario deployment (optional - only needed for create_scenario tool)
  • MAKE_TEAM_ID env
    Make.com Team ID for scenario deployment (optional)
  • MAKE_API_URL env
    Make.com API URL - defaults to https://eu1.make.com/api/v2 (optional)
  • LOG_LEVEL env
    Log level - error, info, or debug (optional, defaults to error)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 danishashko 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1395 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1395 个服务器的 4% 更新
  • 基础检查结果等于或优于此分类中其他 1395 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Make MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:MAKE_API_KEY

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.3.3)于9个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者:github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT4天前更新
安装

Desktop Commander

作者:wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT16天前更新
安装

Cloudflare MCP

作者:cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Make.com MCP Server — Build & Deploy Automation Scenarios with AI

⚠️ Disclaimer: This is an unofficial, community-driven project created by a passionate fan of Make.com. It is NOT affiliated with, endorsed by, or officially supported by Make.com.

A Model Context Protocol (MCP) server that gives AI assistants like Claude, GitHub Copilot, and Cursor full access to Make.com module documentation, scenario validation, and one-click deployment. Search 200+ automation modules across 40+ apps, build blueprints with auto-healing, and deploy directly to Make.com — all from your AI chat.

Features

  • 🔍 200+ Modules — Full-text search across 200+ Make.com modules (Slack, Gmail, Google Sheets, Notion, OpenAI, and 35+ more apps)
  • 📋 Module Details — Retrieve parameters, types, descriptions, and usage docs for any module
  • ✅ Blueprint Validation — Check scenarios for missing parameters, unknown modules, structural issues, and router sub-routes before deploying
  • 🛡️ Account-Aware Compatibility — Verify module IDs against your live Make account/region before deployment to prevent "Module not found" scenarios
  • 🚀 Deploy to Make.com — Push validated blueprints directly to Make.com via API
  • 🩹 Auto-Healing — Automatically fixes LLM-generated blueprints: injects missing metadata, adds designer coordinates, strips unsupported properties like router filter
  • 🔀 Router Support — Full support for builtin:BasicRouter with multiple routes and recursive validation
  • 📚 Scenario Templates — Browse reusable scenario templates for common workflows
  • 📖 Guided Prompts — MCP prompts for guided scenario building and module exploration
  • 📊 Resource Catalog — MCP resources for browsing available apps
  • 🧪 43 Tests — Unit + integration test suite with Vitest
  • ⚡ Fast Response — Optimized SQLite with FTS5 full-text search

🚀 Quick Start — Self-Hosting Options

Option A: npx (No Installation Needed!) 🚀

The fastest way to get started — no cloning, no building:

Prerequisites: Node.js installed on your system

# Run directly — no installation needed!

npx -y make-mcp-server

The package includes a pre-built database with all 200+ Make.com modules. Just add it to your MCP client config and go.

Claude Desktop config (claude_desktop_config.json):

Basic configuration (documentation tools only):

{

"mcpServers": { "make-mcp-server": { "command": "npx", "args": ["-y", "make-mcp-server"], "env": { "LOG_LEVEL": "error" } } } }

Full configuration (with Make.com deployment):

{

"mcpServers": { "make-mcp-server": { "command": "npx", "args": ["-y", "make-mcp-server"], "env": { "LOG_LEVEL": "error", "MAKE_API_KEY": "your_api_key_here", "MAKE_TEAM_ID": "your_team_id", "MAKE_API_URL": "https://eu1.make.com/api/v2" } } } }

Note: npx will download and cache the latest version automatically. The package includes a pre-built database with all Make.com module information — no setup required.


Option B: Docker (Isolated & Reproducible) 🐳

Prerequisites: Docker installed on your system

# Build the Docker image

docker build -t make-mcp-server .

Test it works

echo '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}},"id":1}' | docker run -i --rm make-mcp-server

Claude Desktop config:

Basic configuration (documentation tools only):

{

"mcpServers": { "make-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "--init", "-e", "LOG_LEVEL=error", "make-mcp-server" ] } } }

Full configuration (with Make.com deployment):

{

"mcpServers": { "make-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "--init", "-e", "LOG_LEVEL=error", "-e", "MAKE_API_KEY=your_api_key_here", "-e", "MAKE_TEAM_ID=your_team_id", "-e", "MAKE_API_URL=https://eu1.make.com/api/v2", "make-mcp-server" ] } } }

Important: The -i flag is required for MCP stdio communication.


Option C: Local Installation (For Development) 🛠️

Prerequisites: Node.js and Git

# 1. Clone and install

git clone https://github.com/danishashko/make-mcp.git cd make-mcp npm install

2. Build

npm run build

3. Populate the module database (already done if using npm package)

npm run scrape:prod

4. Test it works

npm start

Claude Desktop config:

{

"mcpServers": { "make-mcp-server": { "command": "node", "args": ["/absolute/path/to/make-mcp/dist/mcp/server.js"], "env": { "LOG_LEVEL": "error", "MAKE_API_KEY": "your_api_key_here", "MAKE_TEAM_ID": "your_team_id" } } } }

Note: The Make.com API credentials are optional. Without them, you'll have access to all documentation, search, and validation tools. With them, you'll additionally get scenario deployment capabilities.


Configuration File Locations
PlatformPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json

Restart Claude Desktop after updating configuration.


💻 Connect Your IDE

make-mcp-server works with any MCP-compatible client:

  • Claude Desktop — See configurations above
  • VS Code (GitHub Copilot) — Add to .vscode/mcp.json
  • Cursor — Add to MCP settings
  • Claude Code — Use claude mcp add command
  • Windsurf — Add to MCP configuration

Usage

Then ask your AI assistant things like:

"Create a Make scenario that watches a Slack channel for new messages and logs them to a Google Sheet"

"What modules does Make have for sending emails?"

"Validate this scenario blueprint..."

Tip: The AI will automatically call tools_documentation first to understand how to use the server effectively.

Available Tools

ToolDescription
tools_documentationSTART HERE — Returns comprehensive documentation for all tools, prompts, and resources
search_modulesFull-text search across 200+ Make.com modules
get_moduleGet detailed module info with parameters and docs
check_account_compatibilityCheck if modules are available in your current Make account/region (with suggestions)
validate_scenarioValidate a scenario blueprint before deployment
create_scenarioDeploy a scenario to Make.com via API
search_templatesSearch reusable scenario templates
list_appsList all apps with module counts

Auto-Healing

The create_scenario tool automatically fixes common issues in LLM-generated blueprints:

IssueAuto-Fix
Missing metadata sectionInjects full metadata with version, scenario config, and designer
Missing metadata.designer on modulesAdds { x: 0, y: 0 } coordinates
Router filter in route objectsStrips unsupported filter property (configure filters in Make.com UI)
Missing version on modulesLeft unset — Make.com auto-resolves the latest installed version
Catalog mismatch (IM007, module not available)Checks live modules in your account/region, auto-remaps close matches, retries deploy once

Tip: Do NOT hardcode "version": 1 on modules. Some apps (e.g., HTTP) are on v4+ and specifying the wrong version causes "Module not found" errors.

MCP Prompts

PromptDescription
build_scenarioGuided workflow for creating a Make.com scenario from a natural language description
explain_moduleGet a detailed explanation of any Make.com module with usage examples

MCP Resources

Resource URIDescription
make://appsList of all available apps with module counts

CLI Usage

make-mcp-server              # Start the MCP server (stdio transport)

make-mcp-server --scrape # Populate/refresh the module database make-mcp-server --version # Print version make-mcp-server --help # Show help

Environment Variables

VariableRequiredDefaultDescription
MAKE_API_KEYFor deployment—Make.com API key
MAKE_API_URLNohttps://eu1.make.com/api/v2Make.com API base URL
MAKE_TEAM_IDFor deployment—Default team ID for scenario deployment
DATABASE_PATHNo /data/make-modules.dbSQLite database file path
LOG_LEVELNoinfoLogging level: debug, info, warn, error, silent
MAKE_MODULE_CACHE_TTL_MSNo300000Cache TTL for live module catalog checks (milliseconds)

Development

npm run build         # Compile TypeScript + copy schema + add shebang

npm run build:tsc # TypeScript only (no packaging) npm run start:dev # Start with tsx (no build needed) npm run dev # Start with file watching npm run scrape # Populate DB with tsx (dev) npm run scrape:prod # Populate DB from compiled JS npm run smoke:compat # One-command account compatibility + validation smoke check npm test # Run all 43 tests npm run test:watch # Run tests in watch mode

Publishing to npm
npm run prepublishOnly   # Build + populate DB + verify (runs automatically on npm publish)

npm publish # Publish to npm registry

Testing

The test suite includes 43 tests across 3 files:

  • Database tests (14 tests) — Insert, search, template operations, FTS5 queries
  • Logger tests (7 tests) — Stderr-only output, log levels, data serialization
  • Server integration tests (22 tests) — Full MCP protocol compliance via SDK client
npm test
Fast Verification (2-3 minutes)

Use this when you just changed validation/deploy logic and want confidence quickly:

# 1) Fast regression check

npm test

2) One-command smoke check (compatibility + validation)

npm run smoke:compat

3) (Optional) Manual MCP exploration

npm run start:dev

Then in your MCP client (Claude/Cursor/Copilot), run this sequence:

  1. check_account_compatibility with a known module, e.g. gateway:CustomWebHook
  2. validate_scenario with your blueprint
  3. create_scenario only if compatibility is good

If step 1 reports incompatible modules, use the suggested replacement IDs before deploying.

Architecture

src/

├── mcp/ │ └── server.ts # MCP server with tools, prompts, resources ├── database/ │ ├── schema.sql # SQLite + FTS5 schema │ └── db.ts # Database access layer (npx-safe path resolution) ├── scrapers/ │ └── scrape-modules.ts # Module data population (224 modules) └── utils/ └── logger.ts # Structured stderr-only logger bin/ ├── make-mcp.js # CLI entry point (npx, --help, --version, --scrape) └── postinstall.js # Post-install verification scripts/ ├── build.js # Build: tsc + copy schema + add shebang ├── prepublish.js # Publish prep: build + populate DB + verify └── smoke-compat.js # Fast local smoke test for module compatibility + validation data/ └── make-modules.db # Pre-built SQLite database (bundled in npm package) tests/ ├── database.test.ts # Dat

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx