Sender logoMCP server · Marketing automation

Sender MCP server

Sender in any MCP client, through Memtro: Sender does not publish this server. Memtro's Sender connector reads Sender through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Sender email marketing: subscribers with status and groups, a subscriber by email, groups and segments with their counts, a group's members, campaigns by status with subject, schedule, recipients and opens, clicks and bounces, and automation workflows with their send and open figures; when asked, can add, update, unsubscribe or delete subscribers, add or remove them from groups, create groups, draft, copy, send, schedule, unschedule or delete campaigns, start a workflow for someone, record a custom event, and send a one-off transactional email.

Reads

  • sender_list_subscribersSender subscribers in Sender's default order: email, name, email status (active, unsubscribed, bounced…), when they joined…
  • sender_get_subscriberOne Sender subscriber by email address or id: name, status, transactional status, join date, bounce and unsubscribe dates, and groups.
  • sender_list_campaignsSender email campaigns: subject, status (DRAFT, SCHEDULED, SENDING, SENT), sender, schedule and send time, recipients, and for sent ones opens…
  • sender_get_campaignOne Sender campaign by id: subject, status, sender, reply-to, schedule, recipients, sent count, opens, clicks, bounces, open and click rates…
  • sender_list_groupsSender groups (lists): id, title, subscribers, active, unsubscribed and bounced counts.
  • sender_group_subscribersSubscribers in one Sender group: email, name, status and join date.
  • sender_list_segmentsSender segments (saved audiences): id, name, subscriber and active counts, created and modified.
  • sender_list_workflowsSender automation workflows: id, title, status (DRAFT, ACTIVE, PAUSED), description, emails sent and their opens, clicks and rates.

Acts, when you ask

These change something in Sender. 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.

  • sender_add_subscriberAdds a subscriber to Sender with their email, optional name and groups.
  • sender_update_subscriberUpdates a Sender subscriber by email or id: name, groups (the list given replaces their groups), or status.
  • sender_add_to_groupAdds existing Sender subscribers, by email, to a group (at most 50 at once); addresses that are not subscribers are reported back.
  • sender_remove_from_groupRemoves Sender subscribers, by email, from a group (at most 50 at once); they stay subscribed otherwise.
  • sender_delete_subscribersPermanently deletes Sender subscribers by email (at most 50 at once), with their history; Sender deletes them shortly after.
  • sender_create_groupCreates an empty Sender group (list).
  • sender_create_campaignCreates a draft email campaign in Sender with a subject, sender name, reply-to address (on a domain verified in Sender), plain-text or HTML content…
  • sender_copy_campaignCopies a Sender campaign into a new draft with the same content and audience; nothing is sent.
  • sender_send_campaignStarts sending a Sender campaign now to every subscriber in its groups and segments (people outside the company).
  • sender_schedule_campaignSchedules a Sender campaign to email its whole audience at a date and time (Y-m-d H:i:s, as Sender reads it for the account).
  • sender_unschedule_campaignCancels a scheduled Sender campaign so it is not sent; it stays as a campaign to edit or schedule again.
  • sender_delete_campaignPermanently deletes one Sender campaign with its report.
  • sender_start_workflowAdds an email address to an active Sender workflow and starts it for them, which sends them the workflow's emails.
  • sender_record_eventRecords a custom event (such as product_viewed or plan_upgraded) against a Sender subscriber, by email or id, with an optional value and properties.
  • sender_send_transactional_emailSends one transactional email through Sender, now, from the address and name given (on a domain verified in Sender) to one recipient…

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

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

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

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

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

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

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

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 Sender 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 week's newsletter perform?
  • › Which campaigns are scheduled to go out?
  • › How many subscribers in the Customers group have bounced?
  • › Which automation workflows are active, and what are their open rates?
  • › Unsubscribe jo@example.com from our emails.

Questions

Is this an official Sender MCP server?
No. It is Memtro's MCP server with Memtro's Sender connector behind it: the connector reads Sender through its API with the credentials you connect on Dashboard → Connections, and Sender 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 Sender?
Only when you ask, and only what it has been granted: add a subscriber; update a subscriber's name, groups or status (including unsubscribing them); add subscribers to a group; remove subscribers from a group; delete subscribers; create a group; create a draft campaign; copy a campaign; send a campaign now; schedule a campaign; cancel a scheduled campaign; delete a campaign; start a workflow for an email address; record a custom event for a subscriber; send a transactional email. 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

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time