# Make MCP connector

The Make connector brings your Make scenarios into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can run, check and manage automations by asking, inside their own Make access, with every action logged.

Source: https://elaichi.ai/connectors/make/

## Facts

| | |
| --- | --- |
| Application | Make |
| Category | IPAAS |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Make builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | help.make.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Make is connected

- Run the lead sync scenario now and tell me how it went.
- Which Make scenarios failed in the last 24 hours?
- Turn off the Slack digest scenario until Monday.

## Connect Make in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Make.
2. Optionally set Share with, then press Connect.
3. Approve it in Make. Make's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Make tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Make MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Make MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Make MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Make to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Make tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Make through Elaichi

### Run a scenario the moment it is needed

Operations. Ask for the order sync scenario to run right now instead of waiting for its next schedule, then get told whether it finished cleanly.

### Check which campaign automations ran overnight

Marketing. Ask which Make scenarios ran since yesterday and which ones stopped with an error, so a broken lead handoff is caught before the morning standup.

### Pause a CRM sync during a data cleanup

Sales. Switch off the scenario that writes to the CRM while the team tidies records, and switch it back on when they are done.

### Find the scenario that routes tickets

Support. Ask which Make scenario handles ticket routing, what it is connected to and when it last ran, without digging through the Make dashboard.

### Review every active scenario in one place

IT. List the scenarios running in each Make team, see who owns them and spot the ones nobody has touched in months.

### Confirm the invoice automation finished

Finance. Ask whether the end-of-month invoice scenario completed and how many runs it made, then ask for it to run again if a batch was missed.

## Elaichi vs Zapier MCP vs Composio for Make

All three can connect Make to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Make tools | Allow or restrict single Make tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Make call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Make to Claude?

Open Elaichi, choose Make and sign in to your Make account over OAuth, the same way you would sign in to Make itself. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and Make is ready to use.

### Does Make work with ChatGPT and Cursor as well as Claude?

Yes. Once Make is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Make once and every client picks it up.

### What can an AI agent actually do with my Make account?

With Make connected, an agent can run your scenarios on request, check which ones ran or failed, and turn scenarios on or off. What is available follows what your Make account has set up, and managing scenarios needs a paid Make plan. Short, concrete asks such as run the lead sync scenario now tend to work better than long paragraphs.

### Does connecting Make give the AI access to every scenario and team?

No. Access to Make follows the person who signed in, so the agent only sees the Make teams and scenarios that person can already open. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Make itself allows.

### Can my team share one Make connection?

Yes. One person connects Make in Elaichi and shares it with a team, and nobody else ever handles the credential. Each teammate still signs in to Elaichi as themselves, so every scenario run in the audit log is tied to the person who asked for it.

### Can I stop an agent from changing or deleting scenarios in Make?

Yes. Restrictions in Elaichi apply per action, so you can let people run and check Make scenarios while blocking changes to them. A restricted action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.

### What happens to a Make connection when someone leaves?

Offboarding that person in Elaichi ends their access to Make at once, across every client they used. A shared Make connection keeps working for everyone else on the team. If you disconnect Make in Elaichi, it is removed from every client in one step.

### Does the Make MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Make is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Make?

Yes. Both let Claude, ChatGPT or Cursor use Make. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Make call.

### How is Elaichi different from Composio for Make?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Make: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.