make

This MCP server provides AI-assisted access to Make.com modules, scenario validation, and one-click deployment. It exposes tools to search and inspect Make modules, validate blueprints, and deploy validated scenarios directly to Make.com. Use the tooling to explore 200+ modules, retrieve detailed module parameters and docs, and verify account compatibility with your Make region before deployment. The server also includes auto-healing for common LLM-generated blueprints and supports router configurations, templates, and guided prompts to assist with scenario design. To get started, configure your MCP client to point at the make-mcp-server endpoint (via npx, docker, or a local build), then begin by querying tools_documentation to understand the available capabilities and prompts, followed by search_modules or get_module to explore specific Make modules. When you’re ready to deploy, use create_scenario after validating your blueprint with validate_scenario, and rely on the auto-healing features to correct common issues in the generated configuration.

Prerequisites:

• Node.js installed on your system (for npx usage) or Docker if you prefer containerized runs
• Access to Make.com API credentials if you plan to deploy scenarios (MAKE_API_KEY, MAKE_TEAM_ID, MAKE_API_URL)

Option A — npx (No Installation Needed) 🚀

Prerequisites: Node.js installed

# Run directly — no installation needed!
npx -y make-mcp-server

The package includes a pre-built database with all Make.com modules. You can connect via MCP client config and begin using the documentation, search, validation, and deployment features.

Claude Desktop config (basic):

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

# 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):

{
  "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 (node path):

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

Tips and considerations: - If deploying via Docker, ensure the -i flag is used for MCP stdio communication. - When using npx, your local cache will store the package version; updating to latest occurs automatically when you run again. - For deployments, keep MAKE_API_KEY and MAKE_API_URL secure and avoid committing credentials in configs. - The server includes a pre-built Make.com module database for quick start; you can scrape/update the database with npm scripts if you need the latest modules. - You can customize LOG_LEVEL to control the verbosity of logs (e.g., error, warn, info, debug). - The available tools include documentation access (tools_documentation), module search (search_modules), module details (get_module), deployment validation (validate_scenario), and one-click deployment (create_scenario).