Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Make MCP

by danishashkoversion 1.3.3i★ –iRuns on your computer
Registry nameio.github.danishashko/make-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools
  • You need to fill in: MAKE_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: MAKE_API_KEY, MAKE_TEAM_ID, MAKE_API_URL, LOG_LEVEL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
      }
    }
  }
}

Run this in your terminal

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MAKE_API_KEY secret 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)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account danishashko, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1395 servers in this category
  • Published to the registry more recently than 4% of the other 1395 servers in this category
  • Basic checks equal to or better than 100% of the other 1395 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Make MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MAKE_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.3) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

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

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Only the beginning is shown; read the rest in the repo

Ask PopNx