Skip to content
Drip logo

Drip MCP server

Email and SMS marketing automation for e-commerce

Drip is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
33
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
October 2026

About the Drip MCP server

Connect Drip once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Drip and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Drip tools your AI can run

Once connected, your assistant can call any of these Drip actions by asking in plain language.

  • Apply a tag to subscriber

    Apply a tag to a subscriber

    3 fields

  • Add a subscriber to a campaign

    Add a subscriber to a campaign (Email series)

    5 fields

  • Create or Update Subscriber

    Create or Update Subscriber

    12 fields

  • Create or Update Subscribers (Batch)

    Creates or updates up to 1,000 subscribers in one request. Drip processes the batch in the background.

    2 fields

  • Delete Subscriber

    Permanently deletes a subscriber and their history. This cannot be undone.

    2 fields

  • Find Subscriber

    Finds one subscriber by email address or Drip subscriber ID.

    2 fields

  • Get Broadcast

    Gets one Single-Email Campaign (broadcast) by ID.

    2 fields

  • Get Email Series

    Gets one Email Series Campaign by ID.

    2 fields

  • Get Conversion

    Gets one conversion goal by ID.

    2 fields

  • Get Current User

    Gets the Drip user who owns the API token.

  • Get Form

    Gets one opt-in form by ID.

    2 fields

  • Get Workflow

    Gets one workflow by ID.

    2 fields

  • List Accounts

    Lists the Drip accounts this API token can access.

  • List Broadcasts

    Lists Single-Email Campaigns (broadcasts) one page at a time.

    4 fields

  • List Email Series Subscribers

    Lists the subscribers of one Email Series Campaign one page at a time.

    5 fields

  • List Email Series

    Lists Email Series Campaigns one page at a time.

    4 fields

  • List Conversions

    Lists conversion goals one page at a time.

    4 fields

  • List Custom Fields

    Lists the custom field identifiers used in the Drip account.

    1 field

  • List Custom Event Names

    Lists the custom event action names recorded in the Drip account.

    3 fields

  • List Forms

    Lists the opt-in forms in the Drip account.

    1 field

  • List Subscriber's Email Series

    Lists the Email Series Campaign subscriptions of one subscriber.

    4 fields

  • List Subscribers

    Lists subscribers one page at a time, optionally filtered by status, tags or sign-up date.

    7 fields

  • List Tags

    Lists every tag used in the Drip account.

    1 field

  • List Workflows

    Lists workflows one page at a time.

    4 fields

  • Record Cart Activity

    Sends a cart created or updated event to Drip Shopper Activity, e.g. for abandoned-cart workflows.

    14 fields

  • Record Custom Event

    Records a custom event (such as "Logged in") for a subscriber. Workflows and rules listening for it may run.

    5 fields

  • Record Order Activity

    Sends an order event (placed, updated, paid, fulfilled, refunded or canceled) to Drip Shopper Activity.

    17 fields

  • Remove Subscriber From Email Series

    Removes a subscriber from one Email Series Campaign, or from all of them when no campaign ID is given.

    3 fields

  • Remove Subscriber From Workflow

    Removes a subscriber from a workflow. Nothing happens if they are not on it.

    3 fields

  • Remove Tag From Subscriber

    Removes a tag from a subscriber.

    3 fields

  • Start Workflow for Subscriber

    Starts a subscriber on an active workflow. The workflow may send emails.

    16 fields

  • Unsubscribe From All Emails

    Unsubscribes a subscriber from all Drip mailings.

    2 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Drip events your agent can watch

These start a run the moment something happens in Drip, so work gets picked up on its own.

  • New Subscriber

    Triggers when a subscriber is created in your Drip account.

    1 field

  • Tag Applied

    Triggers when a tag is applied.

    2 fields

  • Completed Email Series

    Triggers when a subscriber completes an Email Series Campaign.

    2 fields

  • Custom Event Performed

    Triggers when a custom event is recorded for a subscriber.

    2 fields

  • Email Link Clicked

    Triggers when a subscriber clicks a link in a Drip email. Can be high volume.

    1 field

  • Removed From Email Series

    Triggers when a subscriber is removed from an Email Series Campaign.

    2 fields

  • Subscribed to Email Series

    Triggers when a subscriber subscribes to an Email Series Campaign.

    2 fields

  • Subscriber Deleted

    Triggers when a subscriber is deleted from your Drip account.

    1 field

  • Subscriber Unsubscribed From All

    Triggers when a subscriber unsubscribes from all mailings.

    1 field

  • Tag Removed

    Triggers when a tag is removed from a subscriber.

    2 fields

Give your assistant Drip

Connect Drip once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Drip MCP, answered.

No. That is the point of it. One Activepieces server exposes Drip alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Drip in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 33 tools, including Apply a tag to subscriber, Add a subscriber to a campaign, Create or Update Subscriber, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.