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 Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect SendPulse in the guided setup, then add your MCP URL to Microsoft Copilot. 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.
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 + Microsoft Copilot
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.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
SENDPULSE_CLIENT_ID, SENDPULSE_CLIENT_SECRET
Step 1 — Get credentials
Setting up takes about 2 minutes.
- Sign in at https://login.sendpulse.com and open Settings, tab API, section Client credentials.
- Copy the ID into
SENDPULSE_CLIENT_IDand the Secret intoSENDPULSE_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
textis plain. The connector cannot encode it for you, so passhtml_base64already 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:SSin the time zone of the account; chatbot timestamps are ISO 8601. - Paging:
limitandoffsetfor the e-mail service,sizeandskipfor 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
successanddata; the e-mail service answers plain lists and objects, with errors aserror_codeandmessage.
Step 2 — Install the adapter
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
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
SendPulsetools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
sendpulse_list_mailing_lists | List the mailing lists (address books) of the account: id, name, all_email_qty, active_email_qty, inactive_email_qty, phone counts… |
sendpulse_get_mailing_list | Read 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_variables | List 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_emails | List the contacts of a mailing list: email, status and status_explain (New, Active, Unsubscribed, Rejected, Blocked and others), and the… |
sendpulse_create_mailing_list | Create a new, empty mailing list (address book) with the given name. Returns its id. Add contacts afterwards with… |
sendpulse_add_emails_to_mailing_list | Add 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_emails | Unsubscribe 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_list | Delete 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_info | Look 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_stats | Read 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_campaigns | List 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_campaign | Read one e-mail campaign with its results: name, message (sender_name, sender_email, subject, body, list_id), status, send_date… |
sendpulse_create_campaign | Create 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_campaign | Cancel 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_templates | List 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_senders | List the sender addresses of the account for campaigns: email, name, status (Active or awaiting confirmation) and is_allowed_for_smtp. Only… |
sendpulse_list_blacklist | List 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_balance | Read 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_details | Read the detailed balance and plan of the account: balance (main, bonus, currency) and, per service (email, smtp, push), the tariff name… |
sendpulse_send_smtp_email | Send 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_emails | List the transactional e-mails sent through the SMTP service, newest first: id, sender, recipient, subject, send_date, smtp_answer_code and… |
sendpulse_get_smtp_email | Read 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_bounces | List 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_unsubscribed | List the recipients who unsubscribed from transactional e-mails or reported them as spam: email, unsubscribe_by_link, unsubscribe_by_user… |
sendpulse_list_smtp_senders | List 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_sms | Send 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_bots | List the WhatsApp chatbots connected to the account: id, name, status, channel_data (the phone number and business name), inbox with the… |
sendpulse_list_whatsapp_chats | List the conversations of a WhatsApp chatbot, most recent first: contact (id, name, phone in channel_data, tags, variables… |
sendpulse_list_whatsapp_messages | Read the messages exchanged with one WhatsApp contact: id, direction (incoming or outgoing), type, data (the content), status, sent_by… |
sendpulse_get_whatsapp_contact_by_phone | Find 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_message | Send 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_bots | List 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_chats | List the conversations of a Telegram chatbot, most recent first: contact (id, name and username in channel_data, tags, variables… |
sendpulse_list_telegram_messages | Read the messages exchanged with one Telegram contact of a chatbot: id, direction (incoming or outgoing), type, data (the content), status… |
sendpulse_send_telegram_message | Send 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?"
FAQ
Where do the credentials come from? SendPulse, Settings, tab API, section Client credentials: copy the ID into SENDPULSE_CLIENT_ID and the Secret into SENDPULSE_CLIENT_SECRET. The connector exchanges them for a one-hour token and renews it by itself. Transactional e-mail needs the SMTP service activated in the account first.
What does it cover? Mailing lists and contacts, campaigns with their statistics, templates, senders, the blacklist and the balance, single transactional e-mails through the SMTP service with their delivery log, bounces and unsubscribes, and the chats and messages of your WhatsApp and Telegram chatbots. A free-form WhatsApp message is only delivered within 24 hours after the contact last wrote.
Which tools install switched off? sendpulse_create_campaign (mails a whole list), sendpulse_cancel_campaign, sendpulse_remove_emails_from_mailing_list and sendpulse_send_sms (costs money per message). Switch them on on the connector page only if the AI should use them.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?