100+ integrations are ready to connect to your AI.Connect your first MCP

Drip MCP server for your AI

See which emails and workflow steps earned the most, look up a customer with their tags and email series, tag and segment people, draft a campaign for a segment, and send your store's orders and carts to Drip.

PopMCPDrip

Which of our emails earned the most revenue last month, and how did their open and click rates compare?

Supported Drip tools

Every documented Drip REST endpoint, with one-call tools for a person's full picture, a workflow's numbers step by step and a draft email with its audience set.

69 tools in the full catalog: 31 read and 38 write. 36 load by default, and the rest are found with tool search.

drip_create_broadcast

Create a draft Single-Email Campaign.

drip_get_broadcast

Read one Single-Email Campaign with its subject, HTML and text body, status, send time, preview link and a plain description of its audience in derived.audience.

drip_get_workflow_details

Read a workflow's whole structure: entry triggers, ordered steps, delays, decisions, goals, forks and split tests.

drip_list_broadcasts

List Single-Email Campaigns (one-time emails, also called broadcasts): id, name, subject, status, send time, preview link.

drip_list_workflows

List automation workflows: id, name, status and creation date.

drip_remove_subscriber_from_workflow

Take a person off a workflow.

drip_schedule_broadcast

Send a draft Single-Email Campaign to real people, at a time or now.

drip_send_test_broadcast

Send a test copy of a Single-Email Campaign to up to 5 addresses.

drip_set_broadcast_audience

Choose who a draft Single-Email Campaign goes to, by segment.

drip_start_subscriber_on_workflow

Start a person on a workflow.

drip_unschedule_broadcast

Take a scheduled Single-Email Campaign back to draft so it does not send.

drip_update_broadcast

Change a draft Single-Email Campaign.

drip_batch_create_or_update_subscribers

Add or update up to 1000 people in one call.

drip_create_or_update_subscriber

Add a person or update one, matched by email, Drip id or visitor UUID.

drip_delete_subscriber

Delete a person from the account.

drip_get_subscriber

Find one person by email address, Drip id or visitor UUID.

drip_list_subscribers

List people in the account (active by default), with email, name, status, tags, custom fields, lead score and lifetime value in cents.

drip_remove_subscriber_from_campaigns

Take a person off one Email Series Campaign, or off all of them when campaign_id is left out.

drip_unsubscribe_subscriber_from_all

Unsubscribe a person from all mailings in the account.

drip_get_campaign

Read one Email Series Campaign: status, sending schedule, double opt-in, email count, people counts, and the forms that feed it.

drip_list_campaigns

List Email Series Campaigns (drip sequences): id, name, status, sending schedule, email count, active and unsubscribed people counts.

drip_record_order_activity

Tell Drip about an order: placed, updated, paid, fulfilled, refunded or canceled.

drip_subscribe_to_campaign

Put a person on an Email Series Campaign, which starts its emails to them.

drip_account_overview

A quick health check of the connected account: active, unsubscribed and undeliverable people, active workflows and email series, scheduled and draft single emails.

drip_prepare_broadcast

Create a draft one-time email with its audience set, in one call.

drip_subscriber_overview

Everything about one person in one call, by email or id: status, deliverable, tags, custom fields, lead score and lifetime value in cents, plus the Email Series Campaigns they are on, with campaign names and the last email sent.

drip_workflow_performance

How a workflow's emails perform: each send-email step in order with its sends, opens, clicks, unsubscribes, orders and revenue in cents, plus a summary.

drip_apply_tag

Apply one tag to one person by email.

drip_list_event_actions

List the custom event names used in the account, such as Started a trial, as plain names.

drip_list_tags

List every tag used in the account, as plain names.

drip_record_event

Record something a person did, such as Logged in or Started a trial.

drip_remove_tag

Remove one tag from one person.

drip_list_conversions

List conversion goals: id, name, status, URL, default value in cents and counting method.

drip_list_segments

List saved segments or find one by name with q.

drip_get_email_metrics

Report email performance over a date range: sends, deliveries, opens, clicks, bot clicks, unsubscribes, bounces, complaints, orders and revenue in cents, as a summary and per email.

drip_list_custom_fields

List the custom field names used in the account, such as first_name or shirt_size.

drip_activate_workflow

Turn a workflow on, so it starts acting on people and sending its emails.

drip_create_workflow_trigger

Add a trigger that starts a workflow, such as a form submission or a tag.

drip_delete_broadcast

Delete a Single-Email Campaign.

drip_get_broadcast_audience

Read who a Single-Email Campaign goes to.

drip_get_workflow

Read one workflow's name, status and creation date.

drip_list_workflow_triggers

List what starts a workflow: trigger id, provider, trigger_type, properties and actions_required (what is left to set up).

drip_pause_workflow

Pause a workflow so it stops acting on people until it is activated again.

drip_update_workflow_trigger

Change a workflow trigger.

drip_batch_unsubscribe_subscribers

Unsubscribe up to 1000 people from all mailings in one call.

drip_list_subscriber_campaign_subscriptions

List the Email Series Campaigns one person is on: campaign_id, status, whether it is complete and the last email sent.

drip_activate_campaign

Start an Email Series Campaign sending.

drip_batch_cart_activity

Send up to 1000 carts in one call.

drip_batch_order_activity

Send up to 1000 orders in one call, such as an import.

drip_batch_product_activity

Send up to 1000 products in one call, such as a catalog import.

drip_list_campaign_subscribers

List the people on an Email Series Campaign (active by default), newest first.

drip_pause_campaign

Pause an Email Series Campaign so no more of its emails go out until it is activated again.

drip_record_cart_activity

Tell Drip a shopper created or updated a cart, which powers cart abandonment emails.

drip_record_product_activity

Tell Drip a product was created, updated or deleted, which powers product automations such as price drop emails.

drip_create_webhook

Make Drip post events to a URL.

drip_delete_webhook

Delete a webhook, so Drip stops posting to its URL.

drip_get_webhook

Read one webhook: the URL it posts to, its events and version.

drip_list_webhooks

List webhooks: id, the URL they post to, and the events they send.

drip_batch_legacy_orders

The older orders API, still working: send up to 1000 orders in one call.

drip_batch_record_events

Record up to 1000 events in one call.

drip_create_or_update_legacy_order

The older orders API, still working: create or update an order.

drip_create_or_update_legacy_refund

The older orders API, still working: record a refund on a legacy order, which lowers the person's lifetime value.

drip_get_account

Read the connected account's settings: name, website URL, default from name and email, postal address, primary email, phone number and creation date.

drip_get_conversion

Read one conversion goal: name, status, URL, default value in cents and counting method.

drip_get_form

Read one signup form in full: text, confirmation, timing, colours and the pages it shows on.

drip_get_segment

Read one segment with a plain description of its rules in derived.summary.

drip_list_accounts

Show the Drip account this connection is pinned to: name, website URL, default from name and email, postal address, primary email.

drip_list_forms

List signup forms: id, headline, description, placement and whether the widget is on.

drip_get_user

Read who this connection acts as: the Drip user's email, name and time zone.

Connect Drip to Claude, ChatGPT and Claude Code

Credentials off one Drip screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.

In Drip open Settings, then User Settings, and copy the API Token near the bottom of the page. Paste it into PopMCP. If you can open several Drip accounts, choose which one each connection is for.

API token••••••••••••3f7a
ConnectionVerified

Then just ask for the work

  • “Which of our emails earned the most revenue last month, and how did their open and click rates compare?”

    • get_email_metrics
  • “Where do people drop off in our welcome workflow? Show each email's opens and clicks in order”

    • list_workflows
    • workflow_performance
  • “What do we know about jane@northwind.co? Show her tags, lifetime value and which email series she is on”

    • subscriber_overview
  • “Draft a November sale email for our VIP customers segment and send me a test copy”

    • prepare_broadcast
    • send_test_broadcast
  • “Tag everyone on this list of 200 webinar signups as Webinar November”

    • batch_create_or_update_subscribers

Use Drip from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

Drip MCP server questions

What teams ask before putting Drip behind an AI client.

How do I connect Drip to Claude or ChatGPT?

Open Settings, then User Settings in Drip, copy the API Token near the bottom of the page and paste it into PopMCP. PopMCP checks it, lists the Drip accounts it can open, and you choose which ones to connect. Copy the token shown rather than generating a new one, because a new token stops anything still using the old one. Your AI client then reaches Drip through your one PopMCP URL.

Can the AI send an email to my whole list by accident?

New connections start read-only, so nothing can be sent until an owner or admin allows write actions. Once they are allowed, creating an email only makes a draft. prepare_broadcast refuses to make one until you name a segment or say everyone. Sending is a separate call, schedule_broadcast, and the AI is told to confirm it with you first.

What is the difference between a broadcast, a campaign and a workflow in Drip?

A broadcast is what Drip now calls a Single-Email Campaign: one email, sent once. A campaign in the API is an Email Series Campaign: a fixed sequence of emails. A workflow is a visual automation with triggers, delays and decisions. Each has its own tools, and their descriptions point at the others so the AI picks the right one.

Can I connect more than one Drip account?

Yes. One API token can open every account your Drip user belongs to. PopMCP lists them and you choose which to connect, each into its own PopMCP workspace. A connection stays bound to its account: the AI never has to name it, and a request for another account is refused rather than answered from the wrong one.

Can it send my store's orders and carts to Drip?

Yes, for a store Drip has no built-in integration with. record_order_activity, record_cart_activity and record_product_activity send one at a time, and the batch tools send up to 1000 in a call. Amounts in these tools are decimals such as 16.99, unlike people's lifetime value and email revenue, which are in cents. Drip queues these, so they appear shortly after and there is nothing to read back.

What limits does Drip put on the API?

Drip allows 3,600 requests an hour, 50 an hour on batch endpoints with up to 1000 records each, 20 an hour per account on email metrics, and 20 an hour and 40 a day on test emails. When a limit is reached the tool says which one and when to try again.

Do I have to run or host the Drip MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

How do I connect Drip to Claude Code?

Connect Drip in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Drip on the consent screen. The Drip tools are then available in that session, and no Drip credential is stored on your machine.

Why do only 36 of the 69 tools load by default?

Loading 69 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 36-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

What is the difference between a tool and a trigger?

A tool is something your AI calls, and there are 69 here. A trigger is something PopMCP watches for you: 39 Drip events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Drip.

Connect Drip to your AI in minutes

Launch a hosted MCP endpoint for Drip, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP