Resources · Make integration

MCP Client Make integrationAutomate MCP Client with Make.

What if your Make scenarios could use the tools of any remote MCP server? The MCP Client Make integration gives you 2 modules, one action and one search. This page shows builders how to connect a server, build a first scenario and pick the right module.

Try the MCP Client integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MCP Client Make integration do?

The MCP Client Make integration links a scenario (the automation you build in Make, a chain of modules) to a remote MCP (Model Context Protocol) server, a server that exposes a set of tools. Once connected, every tool of that server becomes usable in your scenario: you send it data, it sends back an answer you can pass to the next step.

Run one precise tool on demand. With Call a tool, you pick a tool listed by the server and hand it values mapped from an earlier module, for instance a record created in another app. The reply comes back as bundles (one item passed from a module to the next) that any later module can read.

Let AI choose the tools. Execute an action with AI takes a task and, per Make's description, selects and runs the tools it needs on the connected server. Useful when the steps depend on the request itself.

Chain both. A scenario can fetch something with Call a tool, then hand the result to Execute an action with AI for the next move.

Know the limits before you build: the app has no trigger, so something else must start the scenario, and it is in Open Beta, which means its features and pricing may change. It also has no Make an API Call module. The same app has a page on the n8n side too: see the MCP Client n8n integration, and compare the two platforms in n8n vs Make. If a run fails, start with Make troubleshooting.

Connect

How do you connect an MCP server to Make?

  1. 01

    Open the connection window

    In your scenario, add an MCP Client module and click Create a connection. A connection is the link Make keeps to your server, reused by both modules. You can type a label in Connection name if you plan to link several servers.

  2. 02

    Choose or add the server

    In MCP Server, pick one of the verified remote servers and Make fills the URL field for you. For a server that is not listed, click + New MCP Server and paste its URL yourself.

  3. 03

    Add credentials and save

    If extra fields show up under the URL, enter the token or key they ask for. For a manual URL that needs one, use API Key / Access token. Click Save, then sign in and confirm access if a window asks you to.

First scenario

Build your first scenario with MCP Client

GoalWhen another app hands Make new data, MCP Client runs a server tool on it and AI takes the next action.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since MCP Client has no trigger, start with a module from the app that holds your data.

  2. 02

    Add Call a tool

    Click the + to the right of the first module, search MCP Client, choose Call a tool and create your connection. Pick the tool and map values from the first module into it.

  3. 03

    Hand off to the AI module

    Add Execute an action with AI next. Describe the task and map the reply of Call a tool so the AI works from real data rather than a blank prompt.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, so you can check what the server returned before trusting the scenario with live data.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What can you do with the MCP Client modules?

MCP Client gives you 2 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

1 module
MCP Client1

Execute an action with AI

Action

In Make“Executes a task by automatically selecting and running the required tools using AI.”

This action gives the connected server a task in plain words, and AI picks and runs the tools needed to carry it out, according to Make's description. You get the outcome without choosing each tool yourself.

When to use it
the right tool depends on the request, such as a support message that could need one lookup or several.
Watch out
the app is in Open Beta, so test the result with Run once before relying on it.

Searches

1 module
MCP Client2

Call a tool

Search

In Make“Executes a selected tool directly on the MCP server, using its JSON request structure.”

Pick one tool from the server list and run it directly: you stay in control of exactly what executes, and the module returns what the tool answered. Make shows which inputs the tool requires and which are optional.

When to use it
you already know which tool the job needs and want the same call on every bundle.
Watch out
as a search, it can return zero, one or several bundles, so plan for an empty reply downstream.
Need help

Need help automating MCP Client with Make?

A person reads every message.

FAQ

MCP Client and Make: common questions

01Is the MCP Client Make integration free?
Yes. MCP Client is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits. Keep in mind that the app is in Open Beta: Make states that both its features and its pricing may change.
02What do you need to connect MCP Client to Make?
You need a Make account and the URL of a remote MCP server. Pick a verified server from the MCP Server list and the URL is filled in; otherwise add it through + New MCP Server. Some servers also ask for an access token or API key, which you enter in the fields shown under the URL. The documentation lists no other prerequisite. If the server uses OAuth, it may ask for the Make redirect URI before the sign-in goes through.
03Does the MCP Client Make integration trigger in real time?
No, because MCP Client has no trigger at all. Its two modules only run once something else starts the scenario. You can open the flow with a trigger from another app, so MCP Client acts when that app reports a new item, or rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario. On the Free plan, 15 minutes is also the shortest gap allowed.
04What if a module is missing from MCP Client in Make?
It depends on what is missing. The app only has two modules and no Make an API Call module, so there is no generic request to fall back on inside MCP Client. Look first at the tools of your server: Call a tool can run any of them. If the job belongs to another app, use that app's own modules in the same scenario. Since the app is in Open Beta, the modules may still change. For a harder case, the team can help.
05Should you use Make or n8n for MCP Client?
It depends on where the rest of your automations already live. MCP Client exists on Make, with 2 modules: one runs a chosen tool, the other lets AI pick tools for a task. The app also has an n8n counterpart with its own page on this site. Compare what each side offers for your server, then keep your MCP calls on the platform that already runs the scenarios feeding them data, so you connect accounts once.
Same platform

Other docs you might need on this stack.

Browse all integrations