mcpField
M
Make MCP Server (legacy)

Make MCP Server (legacy)

Local
github.com/integromatProductivity174Updated 20w ago
Repository

About Make MCP Server (legacy)

Make MCP Server (legacy) is an MCP server that exposes on-demand Make scenarios as tools that AI assistants can invoke. It is aimed at users who want AI systems to trigger existing automation workflows. The README notes that a newer cloud-based version is available and recommended for most cases.

Key features

  1. 01Lists Make scenarios configured with On-Demand scheduling
  2. 02Resolves scenario input parameters with descriptions
  3. 03Invokes scenarios with parameters supplied by the assistant
  4. 04Returns scenario output as structured JSON

Use cases

  1. 01Letting an AI assistant trigger Make automation workflows
  2. 02Keeping automation logic in Make while exposing it to AI systems

MCP support

This project is an MCP server that exposes Make scenarios as tools to MCP clients such as Claude Desktop.

#make#automation#ai-assistant

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "make": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "<MAKE_API_KEY>",
        "MAKE_ZONE": "<MAKE_ZONE>",
        "MAKE_TEAM": "<MAKE_TEAM>"
      }
    }
  }
}
Run commandnpx -y @makehq/mcp-server
Environment variables to set
MAKE_API_KEYSecret
MAKE_ZONE
MAKE_TEAM

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@makehq/mcp-server

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.