Connector guide8-minute read35 MCP tools7 languages

SendPulse MCP Server: Contacts, Campaigns and Chats

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

HCBy HelpCode teamUpdated 8 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

SendPulse

SendPulse

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

tools

35

Region

INTL

Category

Marketing Automation

Authentication

OAuth 2.0

Required env vars

SENDPULSE_CLIENT_IDSENDPULSE_CLIENT_SECRET
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Guided setup

Connect SendPulse to Claude, ChatGPT or Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect SendPulse in the guided setup, then add your MCP URL to your AI assistant. No code and no server to run.

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for SendPulse

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

SendPulse · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → SendPulse, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

SendPulse

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Setup

Setting up takes about 2 minutes.

  1. Sign in at https://login.sendpulse.com and open Settings, tab API, section Client credentials.
  2. Copy the ID into SENDPULSE_CLIENT_ID and the Secret into SENDPULSE_CLIENT_SECRET.

The connector exchanges them at /oauth/access_token (client credentials) for a token that lasts one hour and renews it by itself.

Where to start: sendpulse_get_balance_details shows the plan and what is left of it. sendpulse_list_mailing_lists gives the list ids, sendpulse_list_campaigns the campaigns.

Mailing lists and contacts: sendpulse_list_mailing_lists, sendpulse_get_mailing_list, sendpulse_list_mailing_list_variables, sendpulse_list_mailing_list_emails,sendpulse_create_mailing_list, sendpulse_add_emails_to_mailing_list, sendpulse_unsubscribe_emails and sendpulse_remove_emails_from_mailing_list (switched off at install). sendpulse_get_email_info and sendpulse_get_email_campaign_stats look one address up across the account.

Campaigns: sendpulse_list_campaigns and sendpulse_get_campaign (with the statistics) are reads. sendpulse_create_campaign mails a whole list and sendpulse_cancel_campaign stops a scheduled one; both are switched off at install. sendpulse_list_templates, sendpulse_list_senders, sendpulse_list_blacklist, sendpulse_get_balance.

Transactional e-mail: sendpulse_send_smtp_email sends one e-mail to one or a few people through the SMTP service, which must be activated in the account first (SMTP, Settings: SendPulse reviews a short application). sendpulse_list_smtp_senders shows the allowed From addresses. sendpulse_list_smtp_emails and sendpulse_get_smtp_email are the delivery log with opens and clicks; sendpulse_list_smtp_bounces and sendpulse_list_smtp_unsubscribed show who cannot be reached.

SMS: sendpulse_send_sms costs money per message and is switched off at install.

Chatbots: sendpulse_list_whatsapp_bots, sendpulse_list_whatsapp_chats, sendpulse_list_whatsapp_messages, sendpulse_get_whatsapp_contact_by_phone and sendpulse_send_whatsapp_message; sendpulse_list_telegram_bots, sendpulse_list_telegram_chats, sendpulse_list_telegram_messages and sendpulse_send_telegram_message. First list the bots for a bot_id, then the chats for a contact_id.

Field notes

  • HTML must be Base64: the SMTP service and campaigns take the HTML of an e-mail Base64-encoded (UTF-8), while text is plain. The connector cannot encode it for you, so pass html_base64 already encoded and keep the HTML short, or use a stored template with variables, which needs no encoding.
  • Contact statuses in a list: New, Active, Unsubscribed, Rejected (hard bounce), Blocked, awaiting confirmation. Campaigns only go to New and Active.
  • Dates are YYYY-MM-DD HH:MM:SS in the time zone of the account; chatbot timestamps are ISO 8601.
  • Paging: limit and offset for the e-mail service, size and skip for chatbots. A contact list returns at most 100 rows per call.
  • WhatsApp: a free-form message is only delivered within 24 hours after the contact last wrote; outside that window WhatsApp requires an approved template.
  • Limits: at most 10 requests per second, and per-minute and per-day quotas that depend on the plan; SendPulse answers 429 when they are used up. A campaign can be created at most 4 times per hour.
  • Chatbot answers are wrapped as success and data; the e-mail service answers plain lists and objects, with errors as error_code and message.

Prerequisites: SENDPULSE_CLIENT_ID, SENDPULSE_CLIENT_SECRET

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick SendPulse and paste in the env vars listed under Prerequisites.

Available tools

ToolWhat it does
sendpulse_list_mailing_listsList the mailing lists (address books) of the account: id, name, all_email_qty, active_email_qty, inactive_email_qty, phone counts…
sendpulse_get_mailing_listRead one mailing list by id: name, the counts of all, active and inactive e-mail addresses, creation date and status. Read-only
sendpulse_list_mailing_list_variablesList the variables (custom fields such as name or city) defined for a mailing list, each with name and type (string, number, date). Use the…
sendpulse_list_mailing_list_emailsList the contacts of a mailing list: email, status and status_explain (New, Active, Unsubscribed, Rejected, Blocked and others), and the…
sendpulse_create_mailing_listCreate a new, empty mailing list (address book) with the given name. Returns its id. Add contacts afterwards with…
sendpulse_add_emails_to_mailing_listAdd contacts to a mailing list without a confirmation e-mail (single opt-in). Each entry is an e-mail address, or an object with email and…
sendpulse_unsubscribe_emailsUnsubscribe contacts from one mailing list: they stay in the list with the status Unsubscribed and receive no more campaigns sent to it.…
sendpulse_remove_emails_from_mailing_listDelete contacts from a mailing list, up to 100 addresses per call. Their variables and history in that list are lost; to stop mailings but…
sendpulse_get_email_infoLook up one e-mail address across the whole account: every mailing list it is in (book_id), its status there (New, Active, Unsubscribed and…
sendpulse_get_email_campaign_statsRead what one e-mail address received: statistic with the number of campaigns sent, opened (open) and clicked (link), whether it is on the…
sendpulse_list_campaignsList the e-mail campaigns of the account: id, name, status (a code: 0 new, 1 in moderation, 2 sending, 3 sent, 16 cancelled by the user)…
sendpulse_get_campaignRead one e-mail campaign with its results: name, message (sender_name, sender_email, subject, body, list_id), status, send_date…
sendpulse_create_campaignCreate an e-mail campaign that is sent to every active contact of a mailing list, at once or at send_date. Uses a stored template…
sendpulse_cancel_campaignCancel a scheduled e-mail campaign that has not started sending yet. A campaign that is already being sent cannot be stopped this way.…
sendpulse_list_templatesList e-mail templates: id, real_id, name, name_slug, lang, category, created and preview. With owner me only the account's own templates…
sendpulse_list_sendersList the sender addresses of the account for campaigns: email, name, status (Active or awaiting confirmation) and is_allowed_for_smtp. Only…
sendpulse_list_blacklistList the e-mail addresses on the account's blacklist: addresses that never receive a campaign, whatever list they are in. The answer is a…
sendpulse_get_balanceRead the money balance of the account in its currency: currency and balance_currency. It pays for extras such as SMS and overage; the…
sendpulse_get_balance_detailsRead the detailed balance and plan of the account: balance (main, bonus, currency) and, per service (email, smtp, push), the tariff name…
sendpulse_send_smtp_emailSend one transactional e-mail through the SendPulse SMTP service to one or a few recipients (not a list). Returns result true and the…
sendpulse_list_smtp_emailsList the transactional e-mails sent through the SMTP service, newest first: id, sender, recipient, subject, send_date, smtp_answer_code and…
sendpulse_get_smtp_emailRead one transactional e-mail by its id: sender, recipient, subject, send_date, the SMTP answer of the receiving server (code and text) and…
sendpulse_list_smtp_bouncesList the transactional e-mails that bounced within 24 hours: the addresses and the SMTP answer that explains each bounce. Without date it…
sendpulse_list_smtp_unsubscribedList the recipients who unsubscribed from transactional e-mails or reported them as spam: email, unsubscribe_by_link, unsubscribe_by_user…
sendpulse_list_smtp_sendersList the sender addresses confirmed for the SMTP service. Only these can be used as from_email in sendpulse_send_smtp_email. The answer is…
sendpulse_send_smsSend an SMS to a list of phone numbers. Every message is charged to the account balance, with the price depending on the country and route…
sendpulse_list_whatsapp_botsList the WhatsApp chatbots connected to the account: id, name, status, channel_data (the phone number and business name), inbox with the…
sendpulse_list_whatsapp_chatsList the conversations of a WhatsApp chatbot, most recent first: contact (id, name, phone in channel_data, tags, variables…
sendpulse_list_whatsapp_messagesRead the messages exchanged with one WhatsApp contact: id, direction (incoming or outgoing), type, data (the content), status, sent_by…
sendpulse_get_whatsapp_contact_by_phoneFind the contact of a WhatsApp chatbot by phone number: id (the contact_id to write to), status, channel_data (name, phone), tags…
sendpulse_send_whatsapp_messageSend a free-form text message through a WhatsApp chatbot to a contact. WhatsApp only delivers free-form messages within 24 hours after the…
sendpulse_list_telegram_botsList the Telegram chatbots connected to the account: id, name, status, channel_data (the bot username), inbox with the count of total and…
sendpulse_list_telegram_chatsList the conversations of a Telegram chatbot, most recent first: contact (id, name and username in channel_data, tags, variables…
sendpulse_list_telegram_messagesRead the messages exchanged with one Telegram contact of a chatbot: id, direction (incoming or outgoing), type, data (the content), status…
sendpulse_send_telegram_messageSend a text message through a Telegram chatbot to one of its subscribers. Returns the message. The contact must have started the bot and…

Example prompts

  • "How did my last three e-mail campaigns perform: opens, clicks and unsubscribes?"
  • "Add these five addresses to the mailing list Newsletter DE."
  • "Which transactional e-mails to [email protected] bounced this week?"
  • "Show the latest WhatsApp chats of my chatbot and the unanswered ones."
  • "How much is left on my SendPulse plan?"

Next steps

Was this guide helpful?

Connect SendPulse to Claude, ChatGPT or Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect SendPulse in the guided setup, then add your MCP URL to your AI assistant. No code and no server to run.

Related guides

Connectors

Connect SendPulse to ChatGPT via MCP

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Connectors

Connect SendPulse to Claude via MCP

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Connectors

Connect SendPulse to Microsoft Copilot via MCP

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Connectors

Connect SendPulse to Cursor via MCP

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Connectors

Connect SendPulse to Gemini CLI via MCP

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.

Connectors

Connect SendPulse to Meta Muse via MCP

Let your AI work with SendPulse: mailing lists and contacts, e-mail campaigns and their statistics, single transactional e-mails through the SMTP service with their delivery log, and the chats of your WhatsApp and Telegram chatbots. Client ID and secret.