Drip MCP connector
The Drip connector brings Drip subscribers, campaigns, broadcasts, forms, goals and orders to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask about and update them inside their own Drip access, with every call logged.
-
How it connects. Connects with an API key. 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 Drip to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Drip once
-
Open Connections, choose Add connection, and pick Drip.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Drip API key. One person generates a token in Drip and pastes it once. Everyone else works through Share with, and never sees it.
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.
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 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.
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.
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.
Use cases
What teams do with Drip through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
AI tools
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.
See it in Elaichi
What connecting Drip gets you
6 screens from the product, each doing one job for your Drip account.
The agent
Ask Drip questions in plain language.
Subscribers, campaigns and broadcast results answered from live Drip records, not last week's export.
- subscribers
- campaigns
- broadcasts
- forms
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 or Cursor
MCP clients
Every MCP client, one governed Drip endpoint.
Claude, ChatGPT and Cursor reach Drip through one org endpoint, no SDK, no shared API key.
Copy the endpoint
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.
- List all Drip campaign subscriptions
- List all Drip accounts
- Get single Drip account by ID
- List all Drip broadcasts
Toolboxes
Each team gets its own Drip toolbox.
Marketing works broadcasts and campaigns, Support looks up subscribers, each from a toolbox scoped to them.
- Marketing
- Ecommerce
- Lifecycle
- Support
Shared connections
Share Drip access, never the API key.
One person connects Drip, teammates work through it, and nobody else sees the credential.
- Marketing
- Ecommerce
- Lifecycle
- Support
Audit log
Every Drip action lands in the log.
When, who, what happened and which subscriber or broadcast, kept 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 real Drip work.
Drip broadcasts are fetched and grouped, a digest drafted, a person approves, it posts back.
Drip digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Drip
Queued
Collections and dashboards
Drip numbers arrive without anyone asking.
Four metrics, 14 days of subscribers created, a team breakdown, refreshed on schedule, no model.
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%
FAQ
Frequently asked questions
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, 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 blocking deleting broadcasts, pausing campaigns or updating subscribers. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt, however it is worded, can reach it.
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 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, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Drip 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.