RuSender MCP

Calculates how the campaign contacts would be split for a given test percent: the number of contacts per variant and the share that receives the winning variant. Read-only, does not modify the campaign — helps to pick a suitable abTest.percent before saving it via campaign update.

Moves a finished campaign to the archive. Only campaigns in COMPLETED or BANNED status can be archived; for A/B and follow-up campaigns the whole family is archived. Archived campaigns are hidden from the default campaign list — pass archived=true to list them.

Calculates how the campaign contacts would be split into daily chunks for the given settings: the number of chunks, the number of contacts and the send date of each chunk. Read-only, does not modify the campaign — helps to check the sending plan before starting the campaign with the same chunkSettings.

Creates an email campaign in DRAFT status. All fields are optional at creation; the required ones (template, sender, subject, at least one contact list) are validated at start. The draft is not sent automatically — start it with the campaign schedule operation. Pass abTest to create an A/B (split) campaign: 2-10 subject variants are tested on a share of the contacts (abTest.percent), then the winning variant is sent to the rest. Follow-up and chunked sending are not stored in the draft — they are configured at start (see the schedule operation).

Deletes a campaign draft. Only campaigns in DRAFT status can be deleted; the campaign's user template is deleted with it. Deletion cannot be undone via API.

Returns opens and clicks grouped by time periods.

Returns a campaign by ID. For composite campaigns also returns their structure: A/B test breakdown with variants and the winner (abTest), the follow-up (followUp), a reference to the base campaign on a part (parent), and family-aggregated statistics (totalStats). Stats are included when withStats=true.

Returns click statistics grouped by link for the specified campaign.

Returns recipient-domain breakdown of campaign statistics.

Returns user email campaigns. Stats are included when withStats=true.

Paginated list of campaign recipients with delivery/engagement status filter. Each recipient gets exactly one status by priority: complaint > unsubscribed > hard_bounced > soft_bounced > error > clicked > error_infrastructure > opened > delivered > not_delivered. This means clicked includes opened (a recipient who clicked will not appear under opened), while unsubscribed and complaint override all other statuses. The exact page count is not returned — use hasMore for navigation. For statuses error, soft_bounced and hard_bounced the SMTP server response (responseSmtp) is returned.

Starts a campaign draft: the campaign goes to moderation and is sent right after approval, or at the specified time (scheduledStartDate) if provided. The draft must already have a template, a sender, a subject and at least one contact list (set them via campaign create/update); an A/B campaign must also have abTest.percent set. Regular campaigns support two optional, mutually exclusive start modes: followUp — resend the email under a different subject to contacts who did not open it; chunkSettings — send in daily chunks of growing size. Neither mode is available for A/B campaigns.

Returns a campaign from the archive. For A/B and follow-up campaigns the whole family is unarchived.

Updates a campaign draft. Only campaigns in DRAFT status can be edited; only the fields present in the request are changed. For A/B (split) campaigns abTest.variants replaces the whole set of subject variants and abTest.percent sets the test share of contacts.

Starts an active chain for the specified contact. A valid RuSender Public API key is required. Fields in data other than email and name are saved as contact properties.

Returns paginated transactional email sending history for a contact.

Deletes multiple contacts by their IDs. Accepts 1 to 1000 IDs per request.

Permanently deletes a contact from all lists.

Returns paginated campaign sending history for a contact.

Step 1 of importing contacts from a file. Only .csv, .tsv, .txt and .xlsx are accepted — check fileName of the uploaded file first and, if its extension is different (.xls, .pdf, .docx, ...), tell the user this file will not be imported and ask for one of the supported formats instead of calling this tool. Takes an already uploaded file id (see public_files_upload_sessions_create) and the target list id, reads the file and returns the import in status awaiting_mapping with preview (first 10 rows as arrays of cell values, column index is 0-based), columnsCount and variables — the variables that already exist in the list. Nothing is imported yet. ALWAYS print the preview in the chat as a markdown table (one column per file column, header = column index 0..N-1, one row per preview row, values verbatim) and list the existing list variables (name and key) — the user must see the actual records to decide the mapping. Then propose the mapping per column, ask about ambiguous columns and new variables, and only after the user agrees call public_contacts_file_imports_start. If the first row is a header, tell the user it will be counted as one error row.

Status and progress of a file import. awaiting_mapping → mapping not submitted yet; queued / processing → running, check again in a few seconds (processedCount of rowsCount); completed → report addedCount, updatedCount, duplicateCount and errorCount to the user (errors are rows without a valid email/phone, e.g. a header row); failed → see failReason.

Step 2: submit the column mapping agreed with the user and start the import (runs in the background). columns lists only the file columns to import, by 0-based index: type is email, phone, name or variable (with variableKey — the key of a list variable). At least one email or phone column is required; a column the user does not need is simply omitted. To put a column into a variable that does not exist yet, declare it in variables (key, display name, optional type) — it is created in the list on start. Ask the user beforehand whether contacts already in the list should be updated with values from the file (updateExisting, default false — existing contacts are only filled where empty). Then poll public_contacts_file_imports_get_by_id until status is completed or failed and report the counters.

Returns a single contact by its identifier.

Returns a paginated list of contacts with optional filters.

Removes the contacts from every list they belong to. Contacts themselves are not deleted. Accepts 1 to 1000 IDs per request.

Returns aggregated contact statistics.

Re-subscribes a previously unsubscribed contact.

Unsubscribes a contact globally.

Updates basic attributes of a contact (name, phone).

Adds a sending domain and generates the DNS records (DKIM, SPF, DMARC) that must be added to the domain's DNS zone. After adding the records, run domain verification.

Deletes an unverified domain. Verified domains cannot be deleted via API because sending keys and senders depend on them.

Returns a user domain with DNS records.

Returns user domains with DNS records.

Runs a DNS check of the domain: DKIM, SPF and DMARC records are resolved and validated, and the verification status is refreshed. May return warnings (e.g. multiple SPF records) and a suggested merged SPF record.

Creates a sending key for a verified domain. The key is created in DISABLED status and becomes ENABLED after platform moderation.

Deletes a sending key. Sending with this key stops immediately; the operation cannot be undone via API.

Returns the user's transactional email sending key.

Returns the user's transactional email sending keys.

Aggregated transactional mail statistics for a sending key over a period (based on precalculated daily data). Without dateFrom/dateTo returns the last 30 days.

Updates the sending key name.

Send a transactional email through a sending key. Provide the email content in mail.html and/or mail.text — at least one of them is required. key_id is the id of a sending key returned by the public_external_mail_keys_list tool: each key is bound to a verified sending domain, so pick the key whose domain matches the domain of the sender (mail.from) email address provided by the user. To attach files, obtain file ids via public_files_* tools and pass them in mail.attachments as integers.

Send a transactional email built from a stored template. Pass the template id in mail.idTemplateMailUser and the substitution values in mail.params. key_id is the id of a sending key returned by the public_external_mail_keys_list tool: each key is bound to a verified sending domain, so pick the key whose domain matches the domain of the sender (mail.from) email address provided by the user. To attach files, obtain file ids via public_files_* tools and pass them in mail.attachments as integers.

Paginated account-wide list of transactional mails sorted by creation date (newest first). Supports filters: keyId (sending key), status (comma-separated statuses), dateFrom/dateTo (creation date period), toEmail (partial recipient email match), fromEmail (exact sender email). The exact page count is not returned - use hasMore for navigation.

Get a file's metadata by id.

List the user's files (previously uploaded attachments). Use search to find a file by name before uploading it again.

Create a one-time upload session (expires in 30 minutes). purpose selects what the session accepts and what the dashboard upload page shows: attachments (default) — 1-20 files, 5 MB total, for campaign/email attachments; contact_import — exactly one contact base file (.csv, .tsv, .txt, .xlsx) up to 40 MB for public_contacts_file_imports_create. Two ways to upload: (a) if you can run shell commands or HTTP requests yourself, POST all files in ONE multipart request to uploadUrl, repeating the field file (e.g. curl -F file=@a.pdf -F file=@b.xlsx <uploadUrl>); uploadUrl has no web page, never give it to the user; (b) otherwise send the user pageUrl — the upload page in the RuSender dashboard — and ask them to upload the files there and tell you when done. In both cases read the session with public_files_upload_sessions_get to obtain files[].id. The session is closed by the first successful upload, so all files must be sent together.

Get the status of an upload session. completed → files[].id are ready to use as attachments (same order as uploaded); pending → nothing has been uploaded yet (if the user is uploading via pageUrl, ask them to finish and check again); expired → create a new session.

Adds campaigns to the specified folder. A campaign can belong to only one folder, so adding moves it from its current folder if any. IDs that do not exist or are not accessible are silently ignored. The affectedCampaigns field contains the number of campaigns actually added.

Removes campaigns from the specified folder without deleting them. IDs that do not exist, are not accessible or are not in the folder are silently ignored. The affectedCampaigns field contains the number of campaigns actually removed.

Creates a new campaign folder.

Soft-deletes a campaign folder. Campaigns in the folder are not deleted, only unlinked from it.

Returns a single campaign folder by its identifier.

Returns a paginated list of campaign folders.

Updates an existing campaign folder.

Adds existing contacts to the specified list. IDs that do not exist or are not accessible are silently ignored. The affectedContacts field contains the number of contacts actually added: contacts that were already in the list are not counted.

Creates a contact or reuses an existing one. The contact is looked up by email within your account: if a contact with this email already exists, it is reused and the name and phone from the request are ignored; otherwise a new contact is created. Adding to the list is idempotent (already a member is a no-op). Variables are applied in both cases. A duplicate email is never an error. The created flag in the response distinguishes the two outcomes.

Imports up to 1000 contacts into the specified list. Unknown variable keys must be declared in the variables spec for auto-creation.

Returns a paginated list of contacts in the specified list, including variable values.

Atomically moves contacts from this list to the target list. Only contacts that are members of the source list are moved; IDs that are not in the source list, do not exist or are not accessible are silently ignored. Contacts already present in the target list are counted as moved. The movedContacts field contains the number of contacts actually moved.

Removes contacts from the specified list without deleting them from your account. IDs that do not exist or are not accessible are silently ignored. The affectedContacts field contains the number of contacts actually removed: contacts that were not in the list are not counted.

Updates a contact in the context of a list, including variable values.

Creates a new contact list.

Soft-deletes a contact list.

Returns a single contact list by its identifier.

Returns a paginated list of contact lists.

Returns contact statistics for the specified list.

Updates an existing contact list.

Creates a user segment with an arbitrary set of conditions.

Returns the segment with all conditions.

Returns user segments with conditions and pagination.

Returns the list of fields available to the user for building conditions, including contact variables. Each item contains the set of applicable operators. For fields with a predefined value dictionary (currently emailProvider), fetch selectable values via GET /segments/filters/{field}/values (publicSegmentsListFilterValues).

Returns the dictionary of selectable values for condition fields with a predefined value list. Currently the only such field is emailProvider — mail providers (Gmail, Mail.ru, Yandex, etc.) localized by the account locale, plus the special entry "Others" (id = -1, slug others) that matches every provider outside the top list, including unknown domains. To filter contacts by mail provider, create or update a segment condition with field = emailProvider, operator = sentTo and value set to the selected value ids joined by commas (e.g. 1,3,-1). Always take the ids from this endpoint — they must not be guessed.

Updates a segment. If conditions is provided, the current set is fully replaced. If omitted, conditions are not modified.

Adds a sender email address. A confirmation email is always sent to the address — the sender becomes verified only after the link in it is clicked. Senders on your own verified domain get better deliverability: prefer such addresses.

Returns a user email sender.

Returns user email senders.

Resends the confirmation email to an unverified sender address. The sender becomes verified only after the link in the email is clicked.

Creates a new HTML template (type=html).

Returns a user template with HTML contents.

Returns user email templates.

Returns user email templates.

Updates an HTML template. Editing builder templates (type=builder) is forbidden.

Creates a new variable definition in the specified list.

Deletes a variable definition and all its values.

Returns all variable definitions for the specified list.

Updates a variable definition (name, default value).

Creates a new webhook. Webhook payload format and supported event types are described in the RuSender docs: https://rusender.ru/docs/api/public-webhooks-create

Returns a user webhook.

Returns user webhooks.

Updates a webhook (partial update). Webhook payload format and supported event types are described in the RuSender docs: https://rusender.ru/docs/api/public-webhooks-update