Drip MCP server

What the model can do

Drip email marketing: subscribers by status, tag or sign-up date, tags and segments, single-email campaigns with their audience, email series and workflows with their status, and email performance (sends, opens, clicks, unsubscribes, orders, revenue) for a period; and, when asked, draft, edit, test, target, schedule, unschedule or delete a single-email campaign, create or update a subscriber, tag or untag one, unsubscribe one or take them out of a series, start or remove someone on a workflow, and activate or pause a workflow or email series.

Reads

• drip_list_subscribersDrip subscribers: email, name, status, tags and when they were created.
• drip_get_subscriberOne Drip subscriber by email address or Drip id: name, status, tags and created date.
• drip_list_tagsEvery tag used in the Drip account.
• drip_list_campaignsDrip single-email campaigns (one-off sends; Drip's API calls them broadcasts), newest first: name, subject, status (draft, scheduled, sending, sent…
• drip_list_email_seriesDrip email series campaigns (drip sequences): name, status (draft, active, paused), number of emails, active and unsubscribed subscriber counts.
• drip_list_workflowsDrip workflows (automations): name, status (draft, active, paused) and when created.
• drip_email_metricsDrip email performance for a period: totals across every email sent (sends, deliveries, opens, clicks, unsubscribes, bounces, complaints, orders…
• drip_list_segmentsDrip saved segments: id, name and dates.
• drip_get_campaign_audienceWho a single-email campaign is addressed to: everyone, the saved segments it names…

Acts, when you ask

These change something in Drip. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• drip_create_campaign_draftCreate a single-email campaign in Drip as a DRAFT.
• drip_update_campaign_draftChange a DRAFT single-email campaign's name, subject, preheader or body.
• drip_set_campaign_audienceSet who a DRAFT single-email campaign will go to: everyone eligible, or the people in any of the named saved segments (ids from drip_list_segments).
• drip_send_test_campaignEmail a test copy of a single-email campaign to 1 to 5 addresses…
• drip_schedule_campaignSchedule a DRAFT single-email campaign to send, or send it now.
• drip_unschedule_campaignTake a scheduled single-email campaign back to draft so it does not send.
• drip_delete_campaignDelete a single-email campaign.
• drip_upsert_subscriberCreate a Drip subscriber, or update the one with this email.
• drip_tag_subscriberApply a tag to one subscriber by email.
• drip_remove_tagRemove a tag from one subscriber (by email or Drip id).
• drip_unsubscribe_subscriberUnsubscribe one person (by email or Drip id) from ALL Drip mailings.
• drip_remove_from_seriesTake one person (by email or Drip id) out of one email series, so its remaining emails are not sent to them.
• drip_start_workflowStart one person (by email) on a workflow; the workflow then emails them as it is built to.
• drip_remove_from_workflowTake one person (by email or Drip id) off a workflow so its later steps do not reach them.
• drip_set_workflow_stateActivate or pause a Drip workflow.
• drip_set_email_series_stateActivate or pause a Drip email series.

Connect it

First connect Drip on Dashboard → Connections, then add Memtro to your client once. The Drip tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Drip connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How did last month's emails perform on opens, clicks and revenue?
• › Which active subscribers are tagged trial-started?
• › Which email series are active, and how many subscribers are in each?
• › Create a draft campaign called November product update and send me a test
• › Unsubscribe dan.fletcher@acme.com from all mailings

Questions

Is this an official Drip MCP server?

No. It is Memtro's MCP server with Memtro's Drip connector behind it: the connector reads Drip through its API with the credentials you connect on Dashboard → Connections, and Drip publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Drip?

Only when you ask, and only what it has been granted: create or edit a draft single-email campaign (sends nothing by itself); set a draft campaign's audience to everyone or to saved segments; send a test copy of a campaign to up to five team addresses; schedule a single-email campaign or send it now to its audience, or unschedule it back to draft; delete a single-email campaign that is not sending; create or update a subscriber, apply or remove a tag (either can start a workflow that emails them); unsubscribe someone from all mailings, or remove them from one email series; start someone on a workflow or take them off it; activate or pause a workflow or an email series (activating starts emailing people). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Marketing automation

• ActiveCampaign MCP server
• Brevo MCP server
• Customer.io MCP server
• Marketo Engage MCP server
• Account Engagement (Pardot) MCP server
• Mailchimp MCP server