Make MCP Server

What is Make MCP Server about?

Make MCP Server connects to a Make account, discovers scenarios configured with On‑Demand scheduling, and exposes them to AI assistants as callable tools. It resolves input parameters, provides descriptive metadata, and returns scenario outputs in structured JSON, allowing seamless interaction between AI systems and existing automation workflows.

How to use Make MCP Server?

1. Prerequisites: Node.js installed, a Make API key with scenarios:read and scenarios:run scopes, and an MCP client (e.g., Claude Desktop).
2. Add configuration to the mcpServers section of the client’s 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>"
         }
       }
     }
   }
   

3. Replace the placeholder values with your actual Make API key, zone (e.g., eu2.make.com), and team ID.
4. Run the client; the MCP server will start and make your eligible scenarios callable by the AI assistant.

Key features of Make MCP Server

• Automatic discovery of On‑Demand Make scenarios.
• Parameter resolution with human‑readable descriptions for AI consumption.
• Invocation of scenarios with validated inputs.
• Structured JSON output for easy parsing by AI assistants.
• Simple Node.js deployment via npx.

Use cases of Make MCP Server

• AI‑driven automation: Allow conversational AI agents to trigger complex workflows without exposing internal logic.
• Customer support bots: Enable bots to run specific Make scenarios (e.g., generating reports, updating CRM entries) on‑the‑fly.
• Internal tooling: Provide employees with a natural‑language interface to run approved automation tasks.
• Bidirectional AI‑workflow integration: Capture results from Make and feed them back into AI models for further reasoning.

FAQ from the Make MCP Server

Q: Do I need to host this server myself? A: Yes, the server runs locally via Node.js; you can host it on any machine that can reach the Make API.

Q: Which scenarios are exposed? A: Only those configured with the On‑Demand scheduling option are made available to AI assistants.

Q: How are credentials secured? A: API keys are supplied via environment variables, keeping them out of code and configuration files.

Q: Can I use this with other AI clients besides Claude Desktop? A: Any MCP‑compatible client can interact with the server, as long as it follows the Model Context Protocol.

Q: Is there a newer version of this server? A: Yes, a modern cloud‑based version is recommended for most use cases. See the link in the README for details.

Make MCP Server (legacy)

A modern, cloud-based version of the Make MCP Server is now available. For most use cases, we recommend using this new version.

A Model Context Protocol server that enables Make scenarios to be utilized as tools by AI assistants. This integration allows AI systems to trigger and interact with your Make automation workflows.

How It Works

The MCP server:

• Connects to your Make account and identifies all scenarios configured with "On-Demand" scheduling
• Parses and resolves input parameters for each scenario, providing AI assistants with meaningful parameter descriptions
• Allows AI assistants to invoke scenarios with appropriate parameters
• Returns scenario output as structured JSON, enabling AI assistants to properly interpret the results

Benefits

• Turn your Make scenarios into callable tools for AI assistants
• Maintain complex automation logic in Make while exposing functionality to AI systems
• Create bidirectional communication between your AI assistants and your existing automation workflows

Usage with Claude Desktop

Prerequisites

• NodeJS
• MCP Client (like Claude Desktop App)
• Make API Key with scenarios:read and scenarios:run scopes

Installation

To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your 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>"
            }
        }
    }
}

• MAKE_API_KEY - You can generate an API key in your Make profile.
• MAKE_ZONE - The zone your organization is hosted in (e.g., eu2.make.com).
• MAKE_TEAM - You can find the ID in the URL of the Team page.