SendPulse MCP server

What the model can do

SendPulse email marketing and CRM: mailing lists with active and inactive counts, email campaigns with status, sender, subject, send date, cost and delivery, open, click and unsubscribe counts, CRM pipelines and their steps, deals by pipeline, step, status, name, owner or last update, contacts by name or email, team members and task boards; when asked, can comment on a deal or contact, create a task, create, update (move step, mark won or lost, reprice, reassign) or delete a deal, create a contact, create a mailing list, draft, send, schedule or cancel an email campaign, and add, unsubscribe or remove addresses on a mailing list.

Reads

• sendpulse_list_mailing_listsSendPulse mailing lists (address books): id, name, all, active and inactive address counts, created date and status.
• sendpulse_list_campaignsSendPulse email campaigns, newest first by default: id, name and status in words (draft, sent, sending, canceled…).
• sendpulse_get_campaignOne SendPulse email campaign by id: name, status, sender, subject, mailing list, send date, recipient count, price, and delivery statistics (sent…
• sendpulse_list_pipelinesSendPulse CRM pipelines and their steps, in order: ids and names.
• sendpulse_search_dealsSendPulse CRM deals, most recently updated first: name, status (active, won, lost), pipeline and step by name, price and currency, owner id…
• sendpulse_search_contactsSendPulse CRM contacts: name, main email, owner id, tags, companies, number of deals, created and updated.
• sendpulse_list_teamSendPulse team members with CRM access: id and name.
• sendpulse_list_boardsSendPulse CRM task boards and their steps: ids and names.

Acts, when you ask

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

• sendpulse_comment_on_dealAdds a comment to a SendPulse CRM deal, visible to the team; team members mentioned in the text are notified.
• sendpulse_comment_on_contactAdds a comment to a SendPulse CRM contact, visible to the team; team members mentioned in the text are notified.
• sendpulse_create_taskCreates a task on a SendPulse CRM board step, with a priority, optional description, owner (default the key's user), start and due times…
• sendpulse_create_dealCreates an active deal in a SendPulse CRM pipeline step, with an optional name, price and currency (together), owner (default the pipeline's)…
• sendpulse_update_dealChanges a SendPulse CRM deal: move it to another step of its pipeline, mark it won or lost (closing it) or active again, rename it…
• sendpulse_delete_dealPermanently deletes a SendPulse CRM deal with its comments.
• sendpulse_create_contactCreates a SendPulse CRM contact with a first and last name and an owner (default the CRM's default).
• sendpulse_create_mailing_listCreates an empty SendPulse mailing list (address book) with a name that is not already used.
• sendpulse_create_campaign_draftCreates an email campaign in SendPulse as a draft, to a mailing list, from an activated sender address, with a subject and HTML body.
• sendpulse_send_campaignCreates and sends a SendPulse email campaign to every active address on a mailing list (people outside the company), now or at send_date.
• sendpulse_cancel_campaignStops a pending or processing SendPulse email campaign; what has already been delivered stays delivered.
• sendpulse_add_to_mailing_listAdds email addresses (at most 50) to a SendPulse mailing list with single opt-in, so campaigns to that list reach them and list automations…
• sendpulse_unsubscribe_from_mailing_listMarks email addresses (at most 50) as unsubscribed on a SendPulse mailing list; they stay on the list but get no more campaigns from it.
• sendpulse_remove_from_mailing_listPermanently removes email addresses (at most 50) and their list variables from a SendPulse mailing list.

Connect it

First connect SendPulse on Dashboard → Connections, then add Memtro to your client once. The SendPulse 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 SendPulse 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

• › Which deals moved to won this week?
• › How did the September newsletter do on opens and clicks?
• › How many active addresses are on our Customers list?
• › Which deals in the Sales pipeline have not been updated since last month?
• › Add a comment to the BigCo renewal deal saying the contract is with legal.

Questions

Is this an official SendPulse MCP server?

No. It is Memtro's MCP server with Memtro's SendPulse connector behind it: the connector reads SendPulse through its API with the credentials you connect on Dashboard → Connections, and SendPulse 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 SendPulse?

Only when you ask, and only what it has been granted: comment on a CRM deal; comment on a CRM contact; create a CRM task; create a CRM deal; update a CRM deal: step, won or lost, name, price or owner; delete a CRM deal; create a CRM contact; create a mailing list; create a draft email campaign; send or schedule an email campaign to a mailing list; cancel a pending email campaign; add email addresses to a mailing list; unsubscribe email addresses from a mailing list; remove email addresses from a mailing list. 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