make

This MCP server exposes your Make (Integromat) scenarios as callable tools for AI assistants. It connects to your Make account, discovers scenarios configured with On-Demand scheduling, resolves input parameters with descriptive metadata, and enables AI systems to invoke those scenarios with appropriate parameters. The server then returns the scenario output as structured JSON so the AI can interpret results and continue the workflow. For Claude Desktop users, you can configure this MCP server in claude_desktop_config.json under the mcpServers section, providing the necessary API key, zone, and team information. The result is a tool-like interface where each Make scenario becomes a callable endpoint you can trigger with parameter values parsed by the MCP server.

Prerequisites:\n- Node.js installed on your machine (recommended latest LTS).\n- Access to a Make (Integromat) account with scenarios you want to expose.\n- Claude Desktop App (optional) or any MCP client that supports the MCP protocol.\n\nStep-by-step installation:\n1) Install Node.js from https://nodejs.org/ (includes npm and npx).\n2) Ensure npx is available (comes with Node.js).\n3) Use the MCP server package via npx in your client configuration (no global install required):\n - In Claude Desktop or your MCP client, add an entry under mcpServers using the following example:\n\n {\n "mcpServers": {\n "make": {\n "command": "npx",\n "args": ["-y", "@makehq/mcp-server"],\n "env": {\n "MAKE_API_KEY": "<your-api-key>",\n "MAKE_ZONE": "<your-zone>",\n "MAKE_TEAM": "<your-team-id>"\n }\n }\n }\n }\n\n4) Replace the placeholder env values with your Make API key, zone, and team ID.\n5) Save the configuration and restart the MCP client if required.\n6) Test by invoking an On-Demand Make scenario through the MCP interface and verify the returned JSON output.\n\nNote: This legacy server uses the Make API via the @makehq/mcp-server package and is superseded by newer MCP server versions. If you are starting a new integration, consider using the latest Make MCP Server.

Tips and considerations:\n- Make API keys should be kept secret; avoid embedding them in public configs. Prefer environment variable management where possible.\n- MAKE_ZONE should reflect the host region for your Make account (e.g., eu2.make.com).\n- MAKE_TEAM is the numeric team ID found in your Make URL.\n- The MCP server relies on On-Demand scenarios; ensure your Make account has those configured to expose as tools.\n- If you encounter authentication errors, double-check API scopes (scenarios:read, scenarios:run) and that the API key is active.\n- When upgrading to newer MCP server versions, review the new configuration schema and environment variable options, as names and behavior may differ.\n- For Claude Desktop users, ensure the claude_desktop_config.json file is valid JSON and the mcpServers section is properly nested under the top-level mcpServers key.