---
title: "Connect Make MCP Server"
description: "Step-by-step guide to connecting Make.com as an MCP Server with meinGPT"
canonical_url: "https://meingpt.com/en/docs/integrations/make-integration/connect-make-mcp"
language: en
---

# Connect Make MCP Server

This guide shows how to connect a Make.com MCP Server with meinGPT to execute Make scenarios directly from an assistant.

In this guide we set up a simple **HTTP Request** use case as an example —
but of course you can do much more.

## Setup

Create a new assistant in meinGPT and add the **Make** tool under **Connectors (Live)**.

![Create assistant with Make tool](/images/integrations/make-mcp/01-create-assistant.png)

Create a new scenario in Make.com and add the **HTTP Request** module. In this example, we are using a webhook URL. Select the appropriate authentication type and click **Save**.

![Create Make scenario with HTTP module](/images/integrations/make-mcp/02-create-scenario.png)

Click on the **Every 15 minutes** tab at the bottom of the editor and change the schedule settings to **On demand**. Then activate the scenario.

![Set schedule to On demand](/images/integrations/make-mcp/03-schedule-on-demand.png)

![Activate scenario](/images/integrations/make-mcp/04-activate-scenario.png)

Copy the scenario ID from the URL. It is located after `scenarios/` in the address bar (e.g., `5423589`).

![Scenario ID in the URL](/images/integrations/make-mcp/05-scenario-id-url.png)

Update the assistant's system prompt with the scenario ID so that the assistant can easily find the scenario. Then save the assistant.

![System prompt with scenario ID](/images/integrations/make-mcp/06-system-prompt-scenario-id.png)

Open the chat with the assistant. You will be prompted to authenticate the Make connection. Click **Connect**.

![Authenticate Make connection](/images/integrations/make-mcp/07-authenticate-connection.png)

Select your organization in Make and allow the required permissions.

For this HTTP Request example, only the **Run your scenarios** permission is required. Depending on your use case, you may need to grant additional permissions.

![Allow Make permissions](/images/integrations/make-mcp/08-make-permissions.png)

After successful authentication, the connection will be displayed as **Connected**.

![Connection established](/images/integrations/make-mcp/09-connection-established.png)

## Calling the scenario

Once the connection is established, you can call the Make scenario directly in the chat. The assistant will execute the scenario via the MCP connection.

The assistant can only run **existing, activated scenarios** by their scenario ID. It **cannot create or edit scenarios** in Make - you always build the scenario yourself in [Make.com](http://Make.com) first.

![Call scenario in chat](/images/integrations/make-mcp/10-call-scenario.png)

## Connection when sharing an assistant

If you share the assistant with colleagues, **each person authenticates their own, separate Make connection** — just like the initial connection in step 6. The connection is tied to that person's meinGPT account, not to the assistant itself.

This means:
- Each person can connect their own Make account (even from a separate Make Team), independently of other users' connections.
- One person's connection does not expire or get replaced just because another person connects the same assistant in their own chat.
- If one person's connection drops, it does not affect anyone else's connection.

Under **Settings → Connections** you can check at any time whether your personal Make connection still shows as **Connected**.

## Next steps

- [Make Integration – Overview](/en/docs/integrations/make-integration)
- [n8n Integration](/en/docs/integrations/n8n)
- [Power Automate](/en/docs/integrations/power-automate)