M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
M

Make MCP Server

Community
Make automation scenarios callable as tools for AI assistants.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #339 of 438
Stars
★ 173 Popular
Transport
stdio (local process)
Runtime
Node.js
Credentials
API key / credential required
License
MIT
Last commit
42FMRS · D

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

Strongest · Documentation 12/20 Weakest · Reliability 2/20

Reliability
2/20
Security and permissions
8/20
Maintenance
9/20
Documentation
12/20
Setup experience
11/20
Why each score
Reliability 2/20
Only evidence is README and metadata; no source code or tests observed. High uncertainty, cannot confirm functionality, so low score.
Security and permissions 8/20
API key passed via env vars, no hardcoded secrets in docs, but no evidence of least-privilege or confirmation mechanisms. No red flag, but deductions for incomplete scoping.
Maintenance 9/20
Repo not archived, MIT license, some stars and issues, but no visible commit history or release activity, so deductions.
Documentation 12/20
README provides install and config examples but lacks tool parameter details, limitations, troubleshooting, and complete tool list, so deductions.
Setup experience 11/20
Provides Claude Desktop config example but relies on npx and env vars, lacks step-by-step guide and compatibility info, so deductions.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

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.

Setup

Before you start

Runtime：Node.js

MAKE_API_KEY requiredsecret API key generated in your Make profile, with scenarios:read and scenarios:run scopes.
MAKE_ZONE required The zone your organization is hosted in, e.g. eu2.make.com.
MAKE_TEAM required The team ID, found in the URL of the Team page.

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

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add make -e 'MAKE_API_KEY=<your-api-key>' -e 'MAKE_ZONE=<your-zone>' -e 'MAKE_TEAM=<your-team-id>' -- npx -y @makehq/mcp-server

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Check that the tools registered by @makehq/mcp-server (your On-Demand Make scenarios) appear in Claude Desktop's tool list; if not, verify MAKE_API_KEY, MAKE_ZONE and MAKE_TEAM are set correctly.

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.

Things to try

Once connected, you can ask your AI assistant things like:

  • List the Make scenario tools available to me
  • Run one of my On-Demand Make scenarios with the right parameters
  • Trigger my Make automation scenario and show me the JSON output

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 Desktop

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision f436799ef010 Data synced 2026-10-19 Read the FMRS scoring method