Make MCP connector for Manus

Run your Make.com scenarios from a Manus chat

Connect your own Make (make.com) account and Manus can see the scenarios you’ve made available as tools, run them when you ask, pass in the inputs and keep working with the results. On paid Make plans, it can also view and change your scenarios, connections, webhooks and data stores. Every app you’ve connected in Make can be put to work through your scenarios.

First, connect Make in Manus

Add these 20 leads to our CRM and tell the sales channel.

Manus is running your Make scenario “Add leads to CRM” with these inputs:

leads20 itemschannel#sales
Add leads to CRMOn demandRunning
Start scenarioScenarios
Has an email: 18 of 20
Create a contactHubSpot CRM
Send a messageSlack
Return outputScenarios

Run your Make.com scenarios as AI tools

Ask in plain words. Through Make.com MCP, Manus picks the matching scenario, fills in its inputs, runs it and tells you what came back.

  • Add leads to CRM09:02Success8 sec18 added. 2 skipped because they had no email.
  • Build monthly sales report09:06RunningOver 25 secStill running in Make. Manus kept the execution ID.
  • Build monthly sales report09:13Success6 min 40 secOutputs fetched: report link and this month’s totals.
  • Sync Shopify orders09:15Couldn’t run—Not set to On demand, so Make doesn’t offer it as a tool yet.

Run Make scenario from AI chat and use the result

Say what you need. Manus picks the matching scenario, fills in its inputs, runs it and works with whatever the scenario returns.

Let long Make scenarios finish in the background

Make waits up to 25 seconds for a run. Longer scenarios keep going in Make for up to 40 minutes. On paid Make plans, with read access to scenarios selected when you connect, Manus uses the execution ID to fetch the outputs when they’re done.

Your Make scenario inputs and outputs become the tool’s fields

Set them up once in Make, and your Make.com AI workflows get the right data in and a clear result back.

Add leads to CRMActiveOn demand
Description

Adds new leads to HubSpot as contacts and posts a summary in Slack. Skips leads without an email.

Scenario inputs
  • leadsArrayLeads with a name, email and company
  • channelTextSlack channel to notify
Scenario outputs
  • addedNumberHow many contacts were created
  • skippedArrayLeads that weren’t added, with the reason
  • Set it to On demand

    Make offers active scenarios with On demand scheduling as tools. That includes scenarios you started from Make scenario templates.

  • Add inputs and a Return output module

    Scenario inputs are what Manus fills in, and the Return output module sends the results back.

  • Describe what it does

    Make shows your scenario description to Manus as the tool’s description, so say what it does and when to use it.

Manage Make scenarios, webhooks and data stores

On paid Make plans, Manus can also look after your Make.com AI automation setup. Before it changes anything, ask it to list the changes for your OK.

  • Add leads to CRMOn demandActive
  • Sync Shopify ordersEvery 15 minutesActive
  • Weekly newsletterEvery Monday at 9:00Inactive

List Make scenarios and how each one runs

See which scenarios are active, how each one is scheduled and which ones Manus can run right now.

Website form
https://hook.eu1.make.com/••••••••
Data
name, email, company
Used in
Website form to CRM

Find a Make.com webhook URL

Ask for the webhook a scenario listens on, so you can paste it into a form or another app.

Record keyEmail
  • lead-118ana@northwind.co
  • lead-119empty
  • lead-120li@brightpath.io
  • lead-121empty

2 records have no email. Changes are listed for your OK.

Fix records in a Make data store

Find records with missing or wrong values and see each change before anything is saved.

Run a Make scenario every morning with scheduled tasks

Let Manus call the scenario that pulls your data, then write up what it found.

Get a daily orders report from a Make scenario

A Manus scheduled task can run your scenario at the time you choose, then turn what it returns into a short report.

See how scheduled tasks work
Every weekday at 8:00 AMPull orders since the last reportSuccess
Daily orders report, Tuesday
Orders142
Revenue$8,940
Refunds6
Orders, last 7 days

Worth a look: refunds went from 2 to 6, all on the same product.

Connect the Make.com MCP server in Manus

Manus works as the Make.com MCP client, so there’s no server URL or token to set up. Make is already in Manus Connectors, and you approve access on Make’s own screen.

  1. Open Connectors

    In Manus, open Connectors and select Make.

  2. Sign in to Make

    Choose the organization and the scopes Manus can use, then select Allow.

  3. Ask in a task

    Name a scenario or describe the job in plain words.

Allow Manus to use your Make account
OrganizationAcme Marketing
Scopes
  • Run your scenariosEvery Make plan
  • Management scopesScenarios, connections, webhooks, data stores and teams, plus outputs of long runs. Paid Make plans.
Allow

Explore connectors and guides

Questions about the Make MCP connector

Is this the official Make MCP server?

Yes. Manus connects to the Make MCP server, Make’s official MCP (Model Context Protocol) server at mcp.make.com. Make is already in Manus Connectors, so there’s nothing to install or host.

How do I connect Make.com to Manus?

Open Connectors in Manus, select Make and sign in. On Make’s consent screen, choose the organization and the scopes Manus can use, then select Allow. Your Make password is never shared with Manus.

Which Make scenarios can Manus run?

Active scenarios with On demand scheduling in the Make organization you choose, which is what Make’s Run your scenarios scope covers. Give each one scenario inputs and outputs, so Manus knows what to send and what comes back. To limit access further, Make suggests team-specific user accounts on its Teams plan or higher.

Do I need a paid Make plan?

Not to run scenarios: Make’s scenario run tools work on every plan. Viewing and changing scenarios, connections, webhooks, data stores and teams, and fetching the outputs of runs that take longer than 25 seconds, use management scopes, which need a paid Make plan. Make’s pricing page has the current plan details.

What happens if a Make scenario takes a long time?

Make waits up to 25 seconds for a scenario run to return. If it takes longer, the scenario keeps running in Make for up to 40 minutes and Manus gets an execution ID. Fetching the outputs once the run finishes needs read access to scenarios, a management scope on paid Make plans, so select it when you connect.

Can a Make.com webhook trigger start a Manus task?

Yes, through the Manus API rather than this connector. To trigger Manus from Make webhook scenarios or any other scenario, add an HTTP → Make a request step that sends a request with your API key to create a task. The connector on this page works the other way: Manus calls your Make scenarios.

Is there a Make.com integration with Manus?

Yes, and it can go both ways. The Make connector lets Manus find and run your scenarios from a chat. The Manus API lets a scenario start a Manus task, and Manus API webhooks can send the result to a URL you choose when the task finishes.

Is this the same as Make.com AI Agents?

No. Make AI Agents are agents you build and run inside Make, and they can use scenarios as tools too. Here, Manus is the agent: it calls the scenarios you’ve made available through the Make MCP server, as one step in a task it works on for you.

Do I need a Make.com MCP token or a Make.com MCP server URL?

No. Make’s server also accepts an MCP token, which goes into a server URL with your zone or into a request header. In Manus, you sign in with your Make account and approve access on Make’s screen, so there’s nothing to copy or paste.

Do I need Claude or ChatGPT to use Make.com MCP?

No. Claude and ChatGPT have their own ways to add Make, so a “Make.com MCP Claude” or “Make.com MCP ChatGPT” guide covers setup in those apps. In Manus, Make is already in Connectors: sign in once, ask in a chat and the task runs in the cloud.

Make.com webhook not working? Where should I look?

Start with the scenario’s History tab in Make, which lists each run with its status and duration. You can paste what you find into a Manus chat and ask for help working out the cause.

Can I disconnect Make from Manus?

Yes. Open Connectors in Manus, select Make and choose Disconnect.

Connect Make and run your first scenario from chat

Connect Make in Manus