Make.com MCP Server: Connect Claude to 3000+ Apps Without Code
Yes, Make.com has an MCP server that lets Claude trigger your automation scenarios, list workflows, and interact with data stores using plain English.
The Make.com MCP server is a remote server endpoint that exposes your Make automation workflows as tools that Claude can call on demand. Instead of opening a browser and manually clicking "Run" on a scenario, you type a prompt like "Send the daily sales report to Slack" and Claude triggers the scenario, then reports back with the result.
What is the Make.com MCP Server?
Make.com is a no-code automation platform that connects thousands of apps (Slack, Gmail, Airtable, Salesforce, Google Sheets, HubSpot, and more) through visual workflows called scenarios.
The Make MCP Server is an official Make developer feature that implements the Model Context Protocol, an open standard originated by Anthropic that defines a universal interface between AI models and external tools. Once configured, Claude sees your Make scenarios as callable tools, exactly like built-in capabilities. (If you want to test the whole setup quickly, you can try Claude free for a week.)
The practical result: you can automate any of Make's app integrations by talking to Claude. Claude decides when to call each tool based on your intent and executes it server-side.
Prerequisites
Before configuring the integration, you need:
- A Make.com account. Sign up free (no credit card required).
- At least one active Make scenario. The MCP server works by exposing existing scenarios as tools.
- Claude Desktop (macOS or Windows). MCP servers require the desktop app, not the web interface.
- Your Make zone URL, visible in your browser when logged in (e.g.,
eu1.make.com,us1.make.com).
Step 1: Generate a Make MCP Token
Make's MCP server supports two connection methods: an OAuth flow (via https://mcp.make.com) and a token-scoped URL. This guide uses the token method, which works in any client that accepts a plain URL.
To create the token, log in to Make and generate an MCP token. Make's UI changes over time, so confirm the exact menu path and available scopes against the official docs at developers.make.com. Copy the token as soon as it is shown and store it somewhere safe.
Keep this token private. Anyone with it can trigger your scenarios.
Step 2: Find Your Zone URL
Make hosts accounts in different geographic zones. Your MCP endpoint URL depends on which zone your account lives in.
Check the address bar when you're logged in:
| What you see in the address bar | Your zone URL |
|---|---|
eu1.make.com/... | https://eu1.make.com |
eu2.make.com/... | https://eu2.make.com |
us1.make.com/... | https://us1.make.com |
us2.make.com/... | https://us2.make.com |
The token-scoped MCP endpoint URL for your account follows this pattern (your MCP token is part of the URL):
https://{your-zone}.make.com/mcp/u/{your-mcp-token}/sse
For example, if your zone is us1:
https://us1.make.com/mcp/u/YOUR_MCP_TOKEN/sse
Make also publishes a stateless Streamable HTTP variant ending in /stateless and an OAuth endpoint at https://mcp.make.com. Endpoint formats can change, so cross-check the exact path against developers.make.com before you save it.
Step 3: Edit the Claude Desktop Config File
Claude Desktop stores its MCP configuration in a JSON file. Open it:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
If the file doesn't exist yet, create it. Add the Make MCP server entry under mcpServers. Because the MCP token is embedded in the URL, no separate auth header is needed:
{
"mcpServers": {
"make": {
"url": "https://us1.make.com/mcp/u/YOUR_MCP_TOKEN/sse"
}
}
}
Replace us1.make.com with your actual zone and YOUR_MCP_TOKEN with the token you copied in Step 1. Some clients connect to remote MCP servers through a helper such as mcp-remote; if yours does, follow the exact entry shape shown in Make's docs and your client's MCP setup guide.
If you already have other MCP servers configured (e.g., Apify, Bright Data), add the "make" entry alongside them without removing the others.
Step 4: Restart Claude Desktop
Claude only reads the config file at startup. Fully quit the app (don't just close the window; on macOS, use Cmd+Q) and relaunch it.
After restarting, click the plug icon in the Claude Desktop chat input bar. You should see the Make tools listed there, confirming the server is active.
Step 5: Test the Connection
Ask Claude a simple question to verify the connection:
"List my Make scenarios."
Claude will call the Make MCP tool, fetch your scenario list, and display the names and statuses. A response like "I found 3 scenarios in your Make account: ..." means everything is working.
Available Make MCP Tools
The Make MCP server exposes several tools to Claude. The available tool set may expand as the feature exits Early Access, but the core tools include:
| Tool | What It Does | Example Prompt |
|---|---|---|
| List scenarios | Returns all scenarios in your Make account with their status and IDs | "What scenarios do I have in Make?" |
| Run a scenario | Triggers a specific scenario by name or ID | "Run the 'New Lead to HubSpot' scenario." |
| Get scenario status | Checks whether a scenario is active, inactive, or running | "Is the Slack notification scenario enabled?" |
| List data stores | Returns data stores available in your organization | "Show me my Make data stores." |
| Read data store records | Fetches records from a named data store | "Get all rows from the 'Leads' data store." |
| Add/update data store records | Writes new records or updates existing ones | "Add this contact to the 'CRM Backlog' data store." |
Demo: Claude Automating a Multi-App Workflow
Here is a realistic session showing Claude controlling a Make workflow that spans three apps (Google Sheets, Slack, and HubSpot):
Setup: You've built a Make scenario called "Weekly Leads Report" that reads new HubSpot contacts from the past 7 days, formats them into a Google Sheet, and posts a summary to a Slack channel.
Prompt:
"Run the 'Weekly Leads Report' scenario and tell me when it's done."
Claude's response (paraphrased):
"I triggered the 'Weekly Leads Report' scenario (ID: 482991). It completed successfully in 14 seconds. The scenario processed 23 new contacts from HubSpot, updated the 'Q1 Leads' Google Sheet, and posted a summary to the #sales-ops Slack channel."
No browser needed. No manual clicks. The scenario ran on Make's infrastructure; Claude just called the tool and reported back.
Make MCP vs Apify MCP vs Firecrawl MCP
All three are MCP servers, but they serve very different use cases. Here's how they compare:
| Make MCP | Apify MCP | Firecrawl MCP | |
|---|---|---|---|
| Primary use case | Trigger automation workflows across thousands of apps | Run web scrapers and fetch structured datasets | Crawl and extract content from websites for RAG |
| Best for | Teams already using Make for automation | Developers who need structured web data | Teams building knowledge bases from web content |
| App integrations | Thousands (Slack, Gmail, HubSpot, Salesforce, and more) | Web only (30,000+ Apify Actors) | Web only |
| No-code setup | Yes, scenarios built visually in Make | Actors require no coding; custom ones may | Yes |
| Data output format | Scenario execution result / data store records | Structured JSON datasets | Markdown / clean text |
| Access model | MCP token in URL or OAuth | Apify API token or OAuth | Firecrawl API key |
| Pricing | Make plan required (view pricing) | Free tier available | Free tier available |
Choose Make MCP if you want Claude to orchestrate business workflows across SaaS apps: sending emails, updating CRMs, posting to Slack, managing data.
Choose Apify MCP if you need Claude to scrape live data from websites, such as product prices, search results, or social profiles.
Choose Firecrawl MCP if your goal is feeding web content into a RAG pipeline or summarizing documentation sites.
You can run all three simultaneously. Add all three to claude_desktop_config.json and Claude will select the right tool based on your prompt.
Troubleshooting
Claude doesn't show any Make tools after restart
Check that your JSON config is valid (no trailing commas, correct brackets). Use a JSON validator if unsure. Also verify that the zone in the URL matches your actual Make organization, since a mismatched zone or a malformed /mcp/u/{token}/sse path will fail to connect.
"Unauthorized" errors when running a scenario
The MCP token may be expired or have insufficient scopes. Generate a fresh MCP token in Make (see developers.make.com for the current location), update the URL in your config, and restart Claude.
Scenario runs but nothing happens in the connected apps
This usually means the scenario itself has an error, not the MCP connection. Check the Scenario History tab in Make to see the execution log and identify which module failed.
Make MCP tools are missing in the Claude plug icon
The MCP endpoint may not yet be available in your Make zone or plan. Check developers.make.com for the latest availability and connection details, and request access if needed.
FAQ
Does Make.com have an MCP server?
Yes. Make officially offers an MCP server as a developer feature. It lets AI clients like Claude trigger scenarios and interact with data stores via the Model Context Protocol. Connect with a token-scoped URL at https://{zone}.make.com/mcp/u/{mcp-token}/sse or via OAuth at https://mcp.make.com. Confirm the current endpoint against developers.make.com.
How do I connect Claude to Make.com?
Add the Make MCP server to Claude Desktop's config file (claude_desktop_config.json) using your zone-specific, token-scoped endpoint URL. Restart Claude Desktop and the connection activates.
What is the Make MCP server?
The Make MCP server is a remote server endpoint that implements the Model Context Protocol, exposing your Make scenarios and data stores as callable tools to any compatible AI client (Claude Desktop, Cursor, Windsurf). It allows AI agents to trigger automation workflows across Make's thousands of app integrations through natural language.
Is the Make MCP server free?
There is no separate charge for the MCP feature itself; it works against your existing Make account, and you pay for scenario operations the same way you normally would. Make offers a free tier with a monthly operations allowance, plus paid plans. Check Make's pricing page for current limits.
Can Claude trigger Make scenarios automatically?
Yes. With the Make MCP server configured, Claude can trigger any scenario by name or ID when prompted. You can also build agentic workflows where Claude decides which scenario to run based on context. For example, it can route a customer message to either a support or a sales follow-up scenario depending on the content.
What apps can Claude control through Make?
Claude can indirectly trigger any of Make's thousands of app integrations by running the relevant Make scenario. This includes Gmail, Slack, Google Sheets, Airtable, Salesforce, HubSpot, Notion, Jira, Shopify, and many more. The AI controls when the scenario runs; Make handles the actual app connections.
Start Automating With Claude and Make
The Make MCP server turns Claude into a natural language interface for your entire automation stack. Instead of building new integrations from scratch, you describe what you want and Claude routes the request through an existing Make scenario.
Sign up for Make.com free and build your first scenario, then follow the steps above to connect it to Claude Desktop in under ten minutes.
For live web data to feed into your Make workflows (product prices, search results, public datasets), pair Make MCP with the Apify MCP server. Together, they give Claude both automation reach and real-time web access.