← Back to directory
M

Make MCP Server

Community
Make automation scenarios callable as tools for AI assistants.
GitHub source repository ↗
★ 168 Stars Category · Dev Tools Popular Source revision f436799ef010
42FMRS · D
Reliability
2/20
Security and permissions
8/20
Maintenance
9/20
Documentation
12/20
Setup experience
11/20

This server exposes Make scenarios as AI-callable tools, suitable for integrating existing automations. Being legacy, the official recommendation is the new cloud version.

Read the FMRS scoring method →

Make MCP Server (legacy) is a Model Context Protocol server that enables Make scenarios to be utilized as tools by AI assistants. It connects to your Make account, identifies all scenarios configured with 'On-Demand' scheduling, parses input parameters, and allows AI assistants to invoke scenarios with appropriate parameters. Scenario output is returned as structured JSON, enabling proper interpretation by AI.

Tools

The tool list has not been reviewed yet.

Setup

Prerequisites: NodeJS, MCP client (like Claude Desktop), Make API key with scenarios:read and scenarios:run scopes.
Add the example configuration to the mcpServers section of claude_desktop_config.json, and replace environment variables: MAKE_API_KEY generated in Make profile; MAKE_ZONE is the zone your organization is hosted in (e.g., eu2.make.com); MAKE_TEAM ID found in the URL of the Team page.

claude_desktop_config.json
{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": ["-y", "@makehq/mcp-server"],
      "env": {
        "MAKE_API_KEY": "<your-api-key>",
        "MAKE_ZONE": "<your-zone>",
        "MAKE_TEAM": "<your-team-id>"
      }
    }
  }
}

Fit and risk

Best for

  • Developers who want to integrate Make automations with AI assistants.
  • Users who need to quickly turn existing Make scenarios into callable tools.

Not for

  • Users looking for the new cloud-based Make MCP Server (recommended).
  • Users without a Make account or who have not configured On-Demand scenarios.

Required permissions

  • Requires Make API key with scenarios:read and scenarios:run scopes.
  • Environment variables: MAKE_API_KEY, MAKE_ZONE, MAKE_TEAM.

Risks and side effects

  • Exposing API key can lead to unauthorized access to your Make scenarios.
  • Scenario execution may incur costs or side effects; control invocation permissions carefully.

Troubleshooting

  1. Check that NodeJS is installed and compatible.
  2. Verify the API key is valid and has the required scopes.
  3. Confirm MAKE_ZONE and MAKE_TEAM are correctly configured.
  4. Ensure Make scenarios are set to 'On-Demand' scheduling.

Use cases

Trigger Make automation workflows from AI assistants.
Maintain complex automation logic in Make while exposing functionality to AI systems.
Enable bidirectional communication between AI assistants and existing automation workflows.

Supported clients

Claude DesktopFull support