Skip to content

Make MCP connector

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

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Run the lead sync scenario now and tell me how it went.

Working in Make with Elaichi

  • Looked in Make
Ask anything…
Governance / Audit log Last 24 hours
Make Looked in Make Emily Carter · ChatGPT · 9:41 AM Done
Make Looked in Make Megan Brooks · Claude · 9:38 AM Done
Make Looked in Make Ryan Hayes · Cursor · 9:35 AM Done

How to connect Make to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Make MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Make MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

Make MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Make MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Make to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with Make through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Make is logged.

  • Operations

    Run a scenario the moment it is needed

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

  • Marketing

    Check which campaign automations ran overnight

    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.

  • Sales

    Pause a CRM sync during a data cleanup

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

  • Support

    Find the scenario that routes tickets

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

  • IT

    Review every active scenario in one place

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

  • Finance

    Confirm the invoice automation finished

    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.

Try asking

  • “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.”

What connecting Make gets you

5 screens from Elaichi, each doing one job for your Make account.

Elaichi Agent

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Make which scenarios ran overnight.

Plain questions, answered from live Make scenarios and their run history.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint puts Make in every client.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Make through one governed endpoint, no SDK, no shared API key.

ElaichiToolboxes
Name Source template Tools Created

Operations toolbox

Make · scenarios and runs

Make starter 18 Mar 4, 2026

Marketing toolbox

Make · campaign and lead scenarios

— 9 Mar 2, 2026

Sales toolbox

Make · CRM sync scenarios

— 24 Feb 27, 2026

Support toolbox

Make · ticket routing scenarios

Make starter 6 Feb 19, 2026

IT toolbox

Make · webhooks and connections

— 31 Jan 30, 2026

Finance toolbox

Make · invoice and payment scenarios

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Make toolbox.

Operations runs scenarios, Marketing checks its own, nobody sees the other team's automations.

ElaichiConnections
Connection Scope Status Access
MA

Make (Operations)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MA

Make (Marketing)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MA

Make (Sales EMEA)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MA

Make (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
MA

Make (IT)

Connected by Ryan Hayes

Personal • Active Not shared
MA

Make (Finance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share Make without sharing a login.

Teammates run scenarios through one Make connection and never see the credential behind it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Make Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Make Scenarios Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Make Scenarios List Toolbox

Audit log

Every Make run names who started it.

When, who, what happened and which scenario, kept in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Make digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch scenarios

    Make

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Make

    Queued

Workflows

A schedule starts the Make work itself.

Runs are fetched, grouped and drafted into a digest, approved by a person, posted back.

Make health

Refreshed 4 minutes ago · every 15 minutes · from the scenarios collection

Live

Scenarios

1,284 ↓ 12%

Runs

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Scenarios created

Last 14 days

By team

Share of activity

Operations 34%

Marketing 27%

Sales EMEA 21%

Support 18%

Collections and dashboards

Make scenario health, computed without a model.

Four metrics, 14 days of runs and a team breakdown, refreshed on schedule.

Why connect Make's MCP server through Elaichi

Make builds and runs this MCP server. Elaichi sits in front of it, so Make's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Make's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Make's tools at the same Elaichi address as every other connected app. Nobody adds Make's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Make sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Make's server. By default, a tool Make does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Make

    Make builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Make team.

    help.make.com

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Make, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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 Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Questions, answered

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, Microsoft Copilot, 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 restricting changes to them. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, 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.

Put Make in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot