Log inSubmit server
Make MCP Server logo

Make MCP Server

by integromat

Exposes on-demand Make scenarios as structured, callable tools for AI assistants through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Make MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "integromat-make-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@makehq/mcp-server"
      ],
      "env": {
        "MAKE_API_KEY": "YOUR_VALUE_HERE",
        "MAKE_ZONE": "YOUR_VALUE_HERE",
        "MAKE_TEAM": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @makehq/mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The integromat/make-mcp-server MCP server connects AI assistants to Make scenarios configured with On-Demand scheduling. It discovers eligible scenarios, derives their input parameters, and presents them as callable tools. Invocations are sent to Make and returned as structured JSON for the assistant to interpret. Use the integromat/make-mcp-server MCP server when existing Make automation should be accessible from an MCP-compatible client; the repository is marked legacy and points most users to Make’s newer cloud-based server.

Use cases

  • Expose on-demand Make scenarios to an AI assistant
  • Trigger existing Make automation from Claude Desktop
  • Pass assistant-generated parameters into Make workflows
  • Read Make scenario results as structured JSON

Key features

  • Discovers On-Demand Make scenarios
  • Resolves scenario input parameters
  • Invokes Make scenarios through MCP
  • Returns structured JSON output
  • Supports local npx execution

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

21/21 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @makehq/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars174Stargazers on the source repository.
npm downloads323Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Make MCP Server works

What integromat/make-mcp-server MCP server does

The integromat/make-mcp-server MCP server exposes selected Make automation workflows as tools that an AI assistant can call. It works with scenarios using Make’s On-Demand scheduling, rather than publishing every scenario in an account automatically.

The server connects to a Make account, finds the eligible scenarios, and makes their callable operations available through MCP. This lets an assistant use existing Make logic without requiring that logic to be rebuilt as native agent code. Make remains responsible for the workflow and its connected automation steps, while the MCP client handles tool discovery and invocation.

The repository describes this implementation as legacy. Its README recommends Make’s newer cloud-based MCP server for most use cases, so this project is primarily relevant when a local or existing deployment specifically requires the legacy package.

How it works

At startup, the server uses Make account credentials and location details to access the relevant team. It identifies scenarios with On-Demand scheduling and examines their input definitions. Those inputs are resolved into parameter descriptions that an AI assistant can use when deciding how to call a scenario.

When the assistant invokes a scenario, the server passes the supplied parameters to Make. The result is returned as structured JSON, allowing the client to process scenario output instead of receiving only unstructured text. This supports workflows where an assistant both sends information into Make and reads the resulting scenario output.

The integromat/make-mcp-server MCP server is intended for MCP clients such as Claude Desktop. The provided configuration runs it locally through Node.js and npx rather than connecting to a hosted endpoint.

Setup and configuration

The documented setup requires Node.js, an MCP client, and a Make API key with both scenarios:read and scenarios:run scopes. Add the server to the client’s MCP configuration and run the @makehq/mcp-server package with npx.

Three environment variables are needed:

  • MAKE_API_KEY: an API key generated from the Make profile.
  • MAKE_ZONE: the hosting zone for the organization, such as an EU Make zone.
  • MAKE_TEAM: the team identifier, available in the URL of the Make Team page.

The API key must be able to read scenario definitions and run scenarios. The zone and team values determine which Make organization context the server uses.

Tools and capabilities

Available tools are based on the account’s On-Demand scenarios rather than on a fixed, predefined tool list. The server can:

  • Discover eligible Make scenarios.
  • Expose scenario inputs with descriptive parameters.
  • Trigger scenarios with assistant-provided values.
  • Return scenario results as structured JSON.

This model is suitable for exposing existing automation workflows to assistants while keeping the workflow implementation in Make.

Limitations and notes

Only scenarios configured for On-Demand scheduling are described as discoverable by the server. Access also depends on the Make API key having the required scopes and on correct zone and team settings.

The repository is labeled legacy, and its README directs most users toward Make’s newer cloud-based MCP server. Evaluate that newer option before adopting this package for a new deployment.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Make MCP Server

Run `npx -y @makehq/mcp-server` through an MCP client configuration and provide the required Make environment variables.

Yes. The README provides a Claude Desktop configuration using the `@makehq/mcp-server` package.

It identifies scenarios configured with Make’s On-Demand scheduling.

It requires a Make API key with `scenarios:read` and `scenarios:run` scopes, plus the Make zone and team ID.

Related MCP servers

All in Other Tools and Integrations All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMake MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/integromat-make-mcp-server?style=directory)](https://allmcps.com/mcp/integromat-make-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/integromat-make-mcp-server"><img src="https://allmcps.com/api/badge/integromat-make-mcp-server?style=directory" alt="Make MCP Server on AllMCPs" /></a>