Happy slice of mcp pizzaMCP.pizza

make-mcp-server

MCP.Pizza Chef: integromat

Every scenario in your Make account set to on-demand scheduling shows up to the assistant as something it can trigger, with the scenario's own input fields filled in from your conversation and the result read back to you. Starting scenarios is the only thing it does: it cannot create, edit, schedule or even list them for browsing, and if you have no on-demand scenarios the assistant sees nothing at all. A Make account and key are required.

Deprecated · labelled legacy; Make points to hosted developers.make.com/mcp-server
Data
Other

Use This MCP server To

Kick off a saved Make automation without opening Make Run my lead handoff workflow with a name and email Trigger a report scenario and read the result in chat Pass details from our conversation into an existing workflow Test what an on-demand scenario returns before scheduling it

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.

make-mcp-server FAQ

Can I use this to build a new automation?
No. It only starts scenarios you already built in Make, and only those whose scheduling is set to on-demand. Everything else stays invisible to it.
Do I need a key?
Yes, a real Make access key with permission to read and run scenarios, plus your Make zone and team ID. The server quits immediately if any of the three is missing.
Does running scenarios cost money?
Make is a paid product and every run consumes operations from your plan, so an assistant that triggers scenarios repeatedly will draw down your quota.
Will it check with me before it acts?
No. A scenario runs the moment it is called and does whatever it was built to do, which may include sending mail, posting messages or moving data, with no confirmation step.
Is this the current version?
Make labels this repository legacy and points people to its newer hosted server at developers.make.com/mcp-server, though this one still gets occasional updates.
Which apps does it work with?
Any assistant that supports MCP servers. The published example targets Claude Desktop and runs through npx, so there is nothing to build.