Drip MCP connector
The Drip connector brings Drip subscribers, campaigns, broadcasts, forms, goals and orders to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can ask about and update them inside their own Drip access, with every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Pause the welcome campaign until the new offer copy is approved
Working in Drip with Elaichi
-
List all Drip campaign subscriptions
-
List all Drip accounts
-
Get single Drip account by ID
How to connect Drip to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Drip 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.
Drip MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
Drip 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. The plugin directory lives at chatgpt.com/plugins.
Drip 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.
Drip MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 Drip 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.
What teams do with Drip through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Drip is logged.
-
Marketing
Draft and test a broadcast
Write the weekend sale email, create it as a Drip broadcast, send yourself a test, and only schedule it once it reads right.
-
Ecommerce
Keep subscribers current after a purchase
Record orders and refunds against the subscriber so their Drip record reflects what they actually bought and returned.
-
Lifecycle
Pause a campaign before it misfires
Check which Drip campaigns are active, pause the welcome series while the offer changes, and activate it again when the copy is fixed.
-
Support
See what a customer received
Pull a subscriber's campaign subscriptions and recent email metrics to see which Drip emails they got before you reply.
-
Analytics
Compare how last month's emails performed
Fetch Drip email metrics across broadcasts and campaigns and get a plain-language summary of how each one did.
-
Operations
Add signups from other systems
Create or update Drip subscribers from a list of event attendees, filling in the custom fields your team already uses, and record the event against each one.
Try asking
- “Pause the welcome campaign until the new offer copy is approved”
- “Send me a test of the Black Friday broadcast”
- “Which Drip campaigns is this subscriber signed up for right now?”
What connecting Drip gets you
6 screens from Elaichi, each doing one job for your Drip account.
Ask Elaichi to work across your apps.
Pause the welcome campaign until the new offer copy is approved
Send me a test of the Black Friday broadcast
Which Drip campaigns is this subscriber signed up for right now?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Drip questions in plain language.
Subscribers, campaigns and broadcast results answered from live Drip records, not last week's export.
Copy the endpoint
AI apps
Every MCP client, one governed Drip endpoint.
Claude, ChatGPT, Cursor and Microsoft Copilot reach Drip through one org endpoint, no SDK, no shared API key.
Tool catalog
60 Drip tools, ready with no code.
Subscribers, campaigns, broadcasts, forms, goals, orders and refunds covered without writing a line of custom code.
Toolboxes
Each team gets its own Drip toolbox.
Marketing works broadcasts and campaigns, Support looks up subscribers, each from a toolbox scoped to them.
Shared connections
Share Drip access, never the API key.
One person connects Drip, teammates work through it, and nobody else sees the credential.
Audit log
Every Drip action lands in the log.
When, who, what happened and which subscriber or broadcast, kept in an append-only record.
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.
Drip digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch subscribers
Drip
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 Jake Morgan
Approve Deny -
Post the digest
Drip
Queued
Workflows
A schedule starts real Drip work.
Drip broadcasts are fetched and grouped, a digest drafted, a person approves, it posts back.
Drip health
Refreshed 4 minutes ago · every 15 minutes · from the subscribers collection
Subscribers
1,284 ↓ 12%
Campaigns
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Subscribers created
Last 14 days
By team
Share of activity
Marketing 34%
Ecommerce 27%
Lifecycle 21%
Support 18%
Collections and dashboards
Drip numbers arrive without anyone asking.
Four metrics, 14 days of subscribers created, a team breakdown, refreshed on schedule, no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Drip
All three can connect Drip 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 Drip tools | Allow or restrict single Drip 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 Drip 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.
Drip tools for your AI agents
60 tools are ready to call through Elaichi's MCP endpoint the moment you connect Drip, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Drip to Claude?
Open Elaichi, choose Drip from the catalog and paste in an API key from your Drip account settings; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and your Drip subscribers, campaigns and broadcasts are available in the conversation.
Does Drip work with ChatGPT and Cursor as well as Claude?
Yes. Drip is connected to Elaichi once, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing extra to set up for each client.
What can an AI agent actually do with my Drip data?
With Drip connected, an agent can look up subscribers and their campaign subscriptions, add or update subscribers with custom fields, and record orders, refunds and events against them. It can also list, create, update and test broadcasts, activate or pause campaigns, list forms and goals, and fetch email metrics to summarize how a send performed. Short, concrete asks such as pause the welcome campaign work better than long paragraphs.
Does connecting Drip give the AI access to my whole Drip account?
No more than the person who connected it already has. A Drip API key belongs to a Drip account, and the AI works within that account only. Elaichi can narrow what is reachable, for example allowing lookups but not deletes, and it can never widen access beyond what the Drip account behind the key allows.
Can I stop an agent from deleting or changing things in Drip?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Drip subscribers and metrics while restricting deleting broadcasts, pausing campaigns or updating subscribers. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Drip connection when someone leaves?
Offboarding the person in Elaichi ends their access to Drip through every client at once. If they set up a shared Drip connection, it keeps working for everyone else on the team. Disconnecting Drip once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Drip MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Drip 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 Drip?
Yes. Both let Claude, ChatGPT or Cursor use Drip. 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 Drip call.
How is Elaichi different from Composio for Drip?
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 Drip: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Drip 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