In our Stripe guide last week we made a point that surprised some readers: Claude’s connectors are not automation — nothing runs in the background, nothing fires while you’re away. That’s still true. But this week’s connector is the missing piece of that story, because Make MCP connects Claude to the tool whose entire job is background automation. Claude still doesn’t watch your apps — but Make does, 24/7, and Claude can now run, manage, and even help build your Make automations from a chat.
Make has an official connector in Claude’s directory — we verified the live listing and its full tool surface before writing this. Setup is the friendly kind: one click and an OAuth login. Here’s what it unlocks, how to connect it, and the honest notes on where chat ends and Make’s visual editor begins.
What Is Make (And What Does the MCP Add)?
Make is a visual automation platform: you build “scenarios” — workflows like “when a new order arrives in Shopify, add a row in Google Sheets and send a Slack message” — and Make runs them on triggers and schedules, whether you’re at your desk or asleep. It connects thousands of apps and has a free plan generous enough to actually use (around 1,000 operations a month).
MCP (Model Context Protocol) is the standard that lets Claude talk to outside tools — our MCP Setup Guides directory now covers fifteen of them. The Make connector puts your Make account inside Claude: your scenarios become things Claude can list, inspect, switch on and off, and trigger on demand.
The mental model that makes everything click: Make is the engine that runs around the clock; Claude is now a hands-on operator you talk to. The two together cover what neither does alone.
What We Verified in the Live Directory
The connector exposes 67 tools — one of the largest surfaces we’ve seen in the directory. The ones that matter for non-developers cluster into three groups:
- Run and control scenarios: list them, check their status and history, activate or deactivate them, and trigger a run on demand
- Create and update scenarios: yes — Claude can draft new automations and modify existing ones, not just push buttons on what’s already there
- Account management: inspect connections, organizations, and the plumbing your scenarios depend on
That second group is the headline. Every other automation story with Claude has been “Claude triggers a thing.” This is “describe the automation you want, and Claude drafts it in your Make account.”
How to Connect Make MCP to Claude
You’ll need a Make account (free plan is fine) and a paid Claude plan.
- In Claude, open Settings → Connectors and click Browse connectors.
- Search for “Make” and select the official connector (published by Make, pointing to mcp.make.com).
- Click Connect and log in to Make via the OAuth flow. No API keys.
- Start a new chat, check the Make connector is enabled, and test with: “List my Make scenarios and tell me which ones are active.”
What You Can Actually Do
- “Which of my scenarios failed in the last week, and why?” — status checks without opening Make
- “Turn off the Instagram cross-posting scenario until Monday.”
- “Run my invoice-backup scenario now.” — on-demand triggers for things that normally wait for a schedule
- “Draft a scenario: when someone fills my website form, add them to my newsletter list and notify me.” — Claude creates the skeleton in your account
- “Look at my scenarios and tell me which ones overlap or waste operations.” — the audit nobody ever does manually
The Honest Notes
- Complex builds still finish in Make’s editor. Claude can create and modify scenarios, but intricate multi-step workflows — field mappings, filters, error handling — are easier to fine-tune visually. Think “Claude drafts, you polish,” not “never open Make again.”
- Operations still count. Scenarios Claude triggers consume your Make operations quota like any other run. The free plan’s ~1,000 ops go fast if you get trigger-happy.
- The automation runs on Make’s side. Once a scenario is active, it runs whether Claude is in the picture or not — which is exactly what you want, and exactly the difference from every “this is not automation” connector we’ve covered.
Make vs Zapier (The Question Everyone Asks)
Zapier also has a connector in Claude’s directory, and the two platforms have fought over the automation crown for years — different pricing models, different philosophies (Make is visual and operations-based, Zapier is task-based and more guided). Which one belongs in a Claude-centered stack deserves its own article, and it’s coming next week. Short version for now: if you’re starting from zero and cost-sensitive, Make’s free tier is the gentler on-ramp.
FAQ
Is the Make connector free?
The connector costs nothing. You need a Make account (free plan works) and a paid Claude plan for connectors.
Can Claude build a complete automation from scratch?
It can create scenarios and modify them — for simple workflows that’s genuinely usable as-is. For complex ones, treat Claude’s draft as a head start and finish the details in Make’s visual editor.
Does this mean Claude now runs automations in the background?
No — and this distinction matters. Make runs the automations, on its own infrastructure, on its own triggers. Claude is the operator you talk to: it can start, stop, inspect, and build scenarios, but only while you’re in a conversation.
You Might Also Like
More tested MCP guides from our directory:
Related Posts
