Back to MCP directory
publicPublicdnsLocal runtime

make-mcp-server

将您的Make场景转换为可调用的AI助手工具。充分利用您现有的自动化工作流,同时实现AI系统无缝触发和与它们交互的功能。

article

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.
help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client