Zapier MCP connector
The Zapier connector brings the Zapier actions your team has enabled to Claude, ChatGPT and Cursor, so people can run reads and writes across their connected apps as themselves, with every call recorded.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Zapier to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Zapier once
-
Open Connections, choose Add connection, and pick Zapier.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Zapier. Zapier's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Zapier MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Zapier MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Zapier MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect Zapier to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with Zapier through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Operations
Turn on the Zapier actions your team needs
Browse the Zapier actions available for the apps you have connected, switch on the ones your team should use, and keep the rest switched off.
-
Sales
Pull a customer record from a connected app
Ask for an account's latest details from the CRM or billing tool connected through Zapier and get the answer without opening another tab.
-
Support
Log a ticket update through Zapier
After a customer call, run a Zapier write action to update the ticket or post a note in the desk tool your team already uses.
-
Marketing
Add a new lead to the right list
Run a Zapier write action that drops a new contact into your email or ads platform the moment it comes up in a conversation.
-
IT
See which Zapier connections are live
List the app connections behind your Zapier account, review the ones that need attention, and fetch the configuration link when an app needs to be reauthorized.
-
Enablement
Package a repeated job as a Zapier skill
Create and update Zapier skills that bundle the steps your team repeats, so a colleague can ask for the whole job in one line.
Try asking
- “Which Zapier actions are enabled for our CRM?”
- “Pull today's new leads through our enabled Zapier read action”
- “Create a Zapier skill that logs a call note after each demo”
Compare
Elaichi vs Zapier MCP vs Composio for Zapier
All three can connect Zapier 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Zapier tools | Allow or restrict single Zapier 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 Zapier 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Zapier tools for your AI agents
16 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zapier, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Zapier builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Zapier gets you
6 screens from the product, each doing one job for your Zapier account.
The agent
Ask Zapier questions, get live answers.
Type what you need and the agent runs the right Zapier action across your connected apps.
- actions
- connections
- skills
- apps
Ask Elaichi to work across your apps.
Which Zapier actions are enabled for our CRM?
Pull today's new leads through our enabled Zapier read action
Create a Zapier skill that logs a call note after each demo
Also runs in Claude, ChatGPT or Cursor
MCP clients
Zapier works in every MCP client, connected once.
Claude, ChatGPT and Cursor all reach Zapier through one org endpoint, with no shared API key.
Copy the endpoint
Tool catalog
16 Zapier tools, ready without writing code.
Discover actions, run reads and writes, manage connections and skills, all from one catalog.
- Inspect Zapier actions
- Discover Zapier actions
- Enable Zapier action
- Disable Zapier action
Toolboxes
Every team gets its own Zapier toolbox.
Operations manages actions and connections while Sales runs the reads and writes it needs.
- Operations
- Sales
- Support
- Marketing
Shared connections
Share one Zapier connection, never a credential.
One person connects Zapier, shares it with teams, and nobody else sees a secret.
- Operations
- Sales
- Support
- Marketing
Audit log
Every Zapier action lands in the audit log.
See who ran which action, on what, and when, in an append-only record.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Zapier work end to end.
Fetch Zapier actions on a timer, group them, draft a digest, approve, post back.
Zapier digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch actions
Zapier
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Zapier
Queued
Collections and dashboards
Zapier health, computed on a schedule.
Four metrics, 14 days of actions created, a breakdown by team, no model involved.
Zapier health
Refreshed 4 minutes ago · every 15 minutes · from the actions collection
Actions
1,284 ↓ 12%
Connections
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Actions created
Last 14 days
By team
Share of activity
Operations 34%
Sales 27%
Support 21%
Marketing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Zapier to Claude?
In Elaichi, choose Zapier from the catalog and connect it. Zapier opens its own sign-in and approval screen, you approve once, and there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp.
Does Zapier work with ChatGPT and Cursor as well as Claude?
Yes. Once Zapier 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 Zapier once and every client picks it up.
What can an AI agent actually do with my Zapier data?
An agent can look through the Zapier actions available for your connected apps, switch them on or off, and run them: read actions pull records from an app, write actions create or update them. It can also list and manage the connections behind your Zapier account and create, update or delete Zapier skills that bundle repeated steps. Short, concrete asks like "pull today's new leads" work better than long sentences.
Does connecting Zapier give the AI every app in my Zapier account?
No. Access follows the person who signed in to Zapier, so the agent only reaches the apps that person has connected and the actions that have been enabled. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what the person could do in Zapier themselves.
Can I stop an agent from deleting or changing things in Zapier?
Yes. Restrictions in Elaichi work per action, so you can allow Zapier read actions while blocking write actions, or block deleting a Zapier skill while allowing it to be viewed. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Zapier connection when someone leaves?
Offboarding a person in Elaichi ends their access to Zapier at once, in every client they used. A shared Zapier connection keeps working for everyone else on the team. If you want Zapier gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Zapier MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Zapier 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 Zapier?
Yes. Both let Claude, ChatGPT or Cursor use Zapier. 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 Zapier call.
How is Elaichi different from Composio for Zapier?
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 Zapier: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Zapier in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.