Make.com

You can run a Make.com MCP Server locally to empower AI assistants with full Make.com module documentation, scenario validation, and one-click deployment. This server enables you to search modules, inspect parameters, validate blueprints, auto-heal generated blueprints, and deploy validated scenarios directly to Make.com from your AI chat or IDE.

How to use

You connect an MCP-compatible client to the server to access Make.com modules, templates, and deployment capabilities. Use natural language prompts to explore modules, build or validate scenarios, and push validated blueprints to Make.com. The system automatically handles documentation retrieval, parameter understanding, and blueprint validation before deployment. You can also leverage auto-healing to fix common issues in generated blueprints and ensure compatibility with Make.com.

How to install

Prerequisites: Ensure you have Node.js installed on your system. You can also run the server via Docker or use a local development setup if you prefer to modify or extend it.

# Option A: Quick start with npx (no installation required)
npx -y make-mcp-server

# Claude Desktop example configuration (basic tools only)

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

# Full configuration for deployment capabilities

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

# Option B: Run via Docker (isolated & reproducible)
docker build -t make-mcp-server .

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

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

# Full Docker configuration with deployment credentials

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

# Option C: Local development build and run

{
  "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: When using the development flow, ensure you follow the exact command shown for starting the server, including script paths and any required environment variables.

## Additional notes

Environment variables you may use include MAKE\_API\_KEY for deployment, MAKE\_API\_URL for the Make.com API base URL, MAKE\_TEAM\_ID for the target team, and LOG\_LEVEL to control logging verbosity.

Feature highlights you can leverage after connecting an MCP client include full-text module search, module parameter details, scenario validation prior to deployment, and direct deployment of validated blueprints to Make.com.

If you are developing locally, you can run the server in development mode to iterate on features, scrape module data, and test integration with Make.com APIs.

## Configuration and security

Protect your API credentials when deploying. Use secure storage for MAKE\_API\_KEY and limit access to deployment-capable clients. Review and configure router and parameter permissions within Make.com UI as needed to align with your automation goals.

Keep the MCP server updated to benefit from auto-healing improvements, template availability, and expanded module coverage.

## Tools and resources

The MCP server provides a set of tools to help you build and manage automations. You can start by exploring documentation for all tools, search across module catalogs, retrieve detailed module information, validate scenarios, deploy blueprints, explore reusable templates, and list available apps.

## Available tools

### tools\_documentation

START HERE — Returns comprehensive documentation for all tools, prompts, and resources

### search\_modules

Full-text search across 200+ Make.com modules

### get\_module

Get detailed module info with parameters and docs

### validate\_scenario

Validate a scenario blueprint before deployment

### create\_scenario

Deploy a scenario to Make.com via API

### search\_templates

Search reusable scenario templates

### list\_apps

List all apps with module counts