Make MCP

Make MCP turns your Make scenarios into callable tools that Claude or Cursor can trigger directly. If you've already invested in Make (formerly Integromat) workflows, this is the fastest way to let an AI assistant fire them off without writing custom API wrappers. You point the server at your Make account via an API key, and it exposes your scenarios as MCP tools. Claude can then trigger a workflow to, say, add a Notion page, send a Slack message, and update a Google Sheet in one go. The core value is access to Make's 1,000+ app connectors without building individual MCP servers for each. I'd reach for this if I already have a library of Make scenarios doing real work. For example, a "new lead" workflow that writes to Airtable, posts to a CRM, and emails the sales team becomes a single tool Claude can invoke. The server doesn't build scenarios for you, it just makes existing ones callable. That's a narrower use case than it sounds, but for teams already on Make, it's a clean bridge. Quirks: you're limited by Make's execution model. Scenarios run asynchronously, so you won't get instant feedback in the chat. If a workflow takes 30 seconds to complete, Claude won't know the result unless you poll or set up a webhook. The server also assumes you've already designed the scenario with sensible input parameters. If your Make workflow expects a JSON blob with 12 fields, Claude will need to construct that correctly, which can get fiddly. Who shouldn't bother: if you don't already use Make, this isn't a reason to start. Building a Make scenario just to wrap it in MCP is overkill when you could write a direct integration. This is for teams with existing Make infrastructure who want to add conversational triggers. It's also overkill if you only need one or two simple automations. A custom MCP server or a direct API call will be faster to set up and debug.