> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to the MailSenpai MCP server

The MailSenpai MCP connector routes your AI agent's tool calls to MailSenpai's own MCP server through Scalekit. Each user signs in to MailSenpai once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 74 tools.

**Authentication:** OAuth 2.1/DCR
**Categories:** Marketing
**Tools:** 74: 34 read, 9 write, 31 destructive
**Users sign in with:** OAuth
**OAuth app:** Scalekit's or your own
**Built by:** Vendor MCP
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=MAILSENPAIMCP)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the MailSenpai MCP connection

   In **AgentKit > Connections**, create a MailSenpai MCP connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

   Scalekit credentials are available for MailSenpai MCP server, so you don't need to register an OAuth app.

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'mailsenpaimcp'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize MailSenpai MCP:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'mailsenpaimcp_check_blacklist',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "mailsenpaimcp"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize MailSenpai MCP:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="mailsenpaimcp_check_blacklist",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'mailsenpaimcp_check_blacklist',
  toolInput: {},
  connector: 'mailsenpaimcp',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="mailsenpaimcp_check_blacklist",
    tool_input={},
    connection_name="mailsenpaimcp",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `mailsenpaimcp_check_blacklist`

Check Blacklist · Read-only

Checks whether a public IPv4 address or a domain is listed on the public email blocklists (DNSBLs) that MailSenpai queries. For a domain it checks the domain, its registered domain, the IPs of its MX servers and its A record. Returns status (done, in_progress), summary, counts (checks, listed, unreachable, clean) and, for each target, every list with result (listed, clean, unreachable), the reason and the list's official removal page. manual_checks holds the lists that are not queried (for example Spamhaus), each with the link to its official check page. Works on any IP or domain, needs no data from the MailSenpai account and changes nothing. Use it when emails bounce with a blocklist error or before sending from a new IP. It usually answers in 1-5 seconds; if status is in_progress, call again with the returned job.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `job` (`string`, optional): Only to resume: the job returned by a previous call that ended with status in_progress. Avoids starting a second check.
- `language` (`string`, optional): Language of summary and notes: en (default) or it. One of: `en`, `it`.
- `target` (`string`, optional): Public IPv4 address (e.g. 203.0.113.10) or domain (e.g. example.com). IPv6 and private addresses are not supported: for IPv6 pass the domain.

Example input: `{}`

### `mailsenpaimcp_check_domain_dns`

Check Domain Dns · Read-only

Checks the public DNS records that decide whether a domain's email gets delivered: SPF (single record, ending, DNS lookups under the limit of 10, includes that no longer exist), DKIM (the most common selectors, or the one you pass in selector, with key length), DMARC (policy, reports address, inherited from the parent domain) and MX (which servers and spam filters receive the mail). Returns status (checked, public_mailbox, not_found, invalid, dns_unreachable), summary, checks.spf/dkim/dmarc/mx each with result (ok, fix, missing, check) and an explanatory note, tips ordered by priority with the exact values to publish, and the raw records. Works on any domain, does not need data from the MailSenpai account and changes nothing. Use it before sending from a new domain or when emails land in spam.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, optional): Domain to check, e.g. example.com. A URL or an email address also works: the domain is extracted.
- `language` (`string`, optional): Language of notes and tips: en (default) or it. One of: `en`, `it`.
- `selector` (`string`, optional): Optional DKIM selector to try first (the name before ._domainkey), when the sending service uses an uncommon one.

Example input: `{}`

### `mailsenpaimcp_get_campaign`

Get Campaign · Read-only

Returns one campaign by campaign_uid: name, subject, sender, list and segment, status and send date. For opens, clicks and bounces use get_campaign_stats. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.

Example input: `{}`

### `mailsenpaimcp_get_campaign_stats`

Get Campaign Stats · Read-only

Returns the aggregate results of one campaign: recipients processed, delivered, opens and unique opens, clicks, hard/soft bounces, unsubscribes and complaints, with rates. For the individual bounce records use list_campaign_bounces. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.

Example input: `{}`

### `mailsenpaimcp_get_email_spam_test_result`

Get Email Spam Test Result · Read-only

Returns the state and result of a spam test started with start_email_spam_test. status is waiting (no email received yet: ask the user to send it, then call again), analyzing, completed or expired. When completed: score from 0 to 10, rating (excellent, good, needs_work, at_risk), summary, partial (true when authentication or the filter verdict could not be evaluated), the received email (from, subject, sending IP, size), sections with each check (authentication, blocklists, reverse DNS, headers, content), to_do with the fixes in order of impact and the spam filter rules that fired. Only the analysis is stored, never the message text; details are deleted after 24 hours. The score describes this one message, it is not a promise of inbox placement. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `test_token` (`string`, optional): The test_token returned by start_email_spam_test.

Example input: `{}`

### `mailsenpaimcp_get_list`

Get List · Read-only

Returns the full settings of one mailing list by list_uid: general info, default sender (from name, from email, reply-to), notification and company details. If you only know the list name, find its list_uid with list_lists first. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_get_list_field`

Get List Field · Read-only

Returns one custom field of a list by field_id: label, tag, type, required flag, default value and options (for dropdowns). Use list_list_fields to find the field_id. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `field_id` (`string`, optional): Numeric ID of the custom field (field_id), e.g. 12. Find it with list_list_fields.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_get_list_segment`

Get List Segment · Read-only

Returns one segment by segment_uid with its name, match mode (all or any) and conditions. Use list_segment_subscribers to see the matching subscribers. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `segment_uid` (`string`, optional): Unique ID of the segment (segment_uid). Find it with list_list_segments.

Example input: `{}`

### `mailsenpaimcp_get_my_mailsenpai_capabilities`

Get My Mailsenpai Capabilities · Read-only

Returns what the connected MailSenpai account may do: customer name, roles, permission scopes, the list UIDs it is restricted to (empty means all lists) and plan limits such as canSendCampaigns, canDelete, requiresApprovalForSend and maxPerPage. Call it first when you are unsure whether a write, send or delete action is allowed. Read-only, no parameters.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mailsenpaimcp_get_subscriber`

Get Subscriber · Read-only

Returns one subscriber by subscriber_uid with email, all custom field values, status, source, IP address and date added. If you only have the email address use search_subscriber_by_email first. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `subscriber_uid` (`string`, optional): Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Example input: `{}`

### `mailsenpaimcp_get_template`

Get Template · Read-only

Returns one saved email template by template_uid, including its name and full HTML content. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_uid` (`string`, optional): Unique ID of the saved email template (template_uid). Find it with list_templates or search_templates.

Example input: `{}`

### `mailsenpaimcp_get_transactional_email`

Get Transactional Email · Read-only

Returns one transactional email by email_uid with recipient, sender, subject, status and sending details. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email_uid` (`string`, optional): Unique ID of the transactional email (email_uid). Find it with list_transactional_emails.

Example input: `{}`

### `mailsenpaimcp_list_blacklisted_subscribers`

List Blacklisted Subscribers · Read-only

Lists the subscribers of a list with status blacklisted (blocked: they never receive emails, e.g. after complaints or hard bounces). Shortcut for search_subscribers_by_status with status=blacklisted. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_campaign_bounces`

List Campaign Bounces · Read-only

Lists the individual bounces recorded for one campaign: subscriber, bounce type (hard, soft or internal) and the receiving server's message. Use get_campaign_stats for totals only. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_campaigns`

List Campaigns · Read-only

Lists the account's campaigns page by page with campaign_uid, name, type and status (draft, pending-sending, sending, sent, paused...), optionally only those of one list. Use get_campaign for the details and get_campaign_stats for the results. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Optional: return only the campaigns of this list (list_uid from list_lists). Omit for all campaigns.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_confirmed_subscribers`

List Confirmed Subscribers · Read-only

Lists the subscribers of a list with status confirmed, i.e. the active contacts who receive campaigns. Shortcut for search_subscribers_by_status with status=confirmed. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_countries`

List Countries · Read-only

Lists the countries known to MailSenpai with country_id, name and code, used for address details (e.g. a list's company info) and to look up zones with list_country_zones. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_country_zones`

List Country Zones · Read-only

Lists the zones (states, provinces, regions) of one country by country_id from list_countries. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `country_id` (`string`, optional): Numeric country_id as returned by list_countries.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_list_field_types`

List List Field Types · Read-only

Returns the custom field types that create_list_field accepts (identifier and name, e.g. text, dropdown, date). Read-only, no parameters.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mailsenpaimcp_list_list_fields`

List List Fields · Read-only

Lists the custom fields of one list (for example EMAIL, FNAME, LNAME) with each field's field_id, tag, label, type and required flag. Use it to learn the tags for subscriber data and the field_id needed in segment conditions. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_list_segments`

List List Segments · Read-only

Lists the segments (saved subscriber filters) of one list with each segment_uid and name. Use get_list_segment for the conditions and list_segment_subscribers to see who matches. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_lists`

List Lists · Read-only

Lists the account's mailing lists page by page, with each list's list_uid, name and display name. Use it to find the list_uid that most other tools need; use get_list for the full settings of one list. Returns data.records plus count and total_pages. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_segment_condition_operators`

List Segment Condition Operators · Read-only

Returns the operators that segment conditions can use (operator_id, name and slug such as contains or greater-than). Read-only, no parameters.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `mailsenpaimcp_list_segment_subscribers`

List Segment Subscribers · Read-only

Returns the subscribers that currently match a saved segment (subscriber_uid, email, status, field values). Use list_subscribers for the whole list, or search_subscribers_by_custom_fields for a one-off filter without saving a segment. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.
- `segment_uid` (`string`, optional): Unique ID of the segment (segment_uid). Find it with list_list_segments.

Example input: `{}`

### `mailsenpaimcp_list_subscribers`

List Subscribers · Read-only

Lists the subscribers of one list page by page, optionally filtered by status; each record has subscriber_uid, email, custom field values, status, source and date added. To find one person use search_subscriber_by_email; to filter by field values use search_subscribers_by_custom_fields. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.
- `status` (`string`, optional): Optional status filter: confirmed, unconfirmed, unsubscribed, blacklisted, unapproved, disabled or moved. Omit to get every status. One of: `confirmed`, `unconfirmed`, `unsubscribed`, `blacklisted`, `unapproved`, `disabled`, `moved`.

Example input: `{}`

### `mailsenpaimcp_list_templates`

List Templates · Read-only

Lists the saved email templates of the account (template_uid, name, screenshot) page by page. Use search_templates to filter by name and get_template for the full HTML. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filters` (`object`, optional): Optional filters, e.g. {"name": "welcome"}. Omit to list everything.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_transactional_emails`

List Transactional Emails · Read-only

Lists transactional emails (single one-to-one messages such as receipts or password resets) with email_uid, recipient, subject, status and send date. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_unconfirmed_subscribers`

List Unconfirmed Subscribers · Read-only

Lists the subscribers of a list with status unconfirmed (signed up but not yet confirmed, so they do not receive campaigns). Shortcut for search_subscribers_by_status with status=unconfirmed. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_list_unsubscribed_subscribers`

List Unsubscribed Subscribers · Read-only

Lists the subscribers of a list with status unsubscribed (opted out; kept for history and no longer emailed). Shortcut for search_subscribers_by_status with status=unsubscribed. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_search_subscriber_by_email`

Search Subscriber By Email · Read-only

Checks whether an email address is in ONE given list and returns its subscriber_uid and status; an error saying the subscriber does not exist means not found. Use search_subscriber_by_email_all_lists when you do not know the list. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_search_subscriber_by_email_all_lists`

Search Subscriber By Email All Lists · Read-only

Finds an email address across ALL lists of the account and returns every match with its list, subscriber_uid and status. Use it when the list is unknown (e.g. privacy or opt-out requests); use search_subscriber_by_email when you know the list. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".

Example input: `{}`

### `mailsenpaimcp_search_subscribers_by_custom_fields`

Search Subscribers By Custom Fields · Read-only

Finds subscribers in one list whose custom field values match exactly, e.g. {"CITY": "Rome"}; with several fields all must match. Use it for ad-hoc lookups; use search_subscriber_by_email for an email address and create_list_segment for a reusable filter. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fields` (`object`, optional): Field tags and the exact values to match, e.g. {"FNAME": "Jane", "CITY": "Rome"}. Get the tags from list_list_fields.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_search_subscribers_by_status`

Search Subscribers By Status · Read-only

Lists the subscribers of one list that have the given status (required). Same result as list_subscribers with a status filter; the list_confirmed/unconfirmed/unsubscribed/blacklisted_subscribers tools are shortcuts for common statuses. Paginated; read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.
- `status` (`string`, optional): Subscriber status: confirmed, unconfirmed, unsubscribed, blacklisted, unapproved, disabled or moved. One of: `confirmed`, `unconfirmed`, `unsubscribed`, `blacklisted`, `unapproved`, `disabled`, `moved`.

Example input: `{}`

### `mailsenpaimcp_search_templates`

Search Templates · Read-only

Finds saved templates matching the given filters, e.g. {"name": "welcome"}, page by page. Use list_templates to browse all templates. Read-only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filters` (`object`, optional): Filters to match, e.g. {"name": "welcome"}.
- `page` (`integer`, optional): Page number to return, starting at 1. Default: `1`.
- `per_page` (`integer`, optional): Results per page (default 10). The server caps it at the plan maximum, usually 50. Default: `10`.

Example input: `{}`

### `mailsenpaimcp_bulk_create_subscribers`

Bulk Create Subscribers · Write

Adds many subscribers to one list in a single call and returns the outcome for each row. The number of rows is capped by the plan (usually 500 per call); split bigger imports. Use create_subscriber for a single contact.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`array`, optional): Array of subscribers, each with EMAIL and optional field tags, e.g. [{"EMAIL": "ann@example.org", "FNAME": "Ann"}, {"EMAIL": "bob@example.org"}].
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_copy_campaign`

Copy Campaign · Write

Duplicates an existing campaign (list, segment, content and settings) into a new DRAFT without send date and returns the new campaign_uid; the copy's name gets a "#1"-style suffix. Use it to reuse a past campaign; use create_campaign to start from scratch. Nothing is sent.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.

Example input: `{}`

### `mailsenpaimcp_copy_list`

Copy List · Write

Creates a copy of a list with its settings, custom fields and segments (subscribers are NOT copied) and returns the new list_uid; the copy's name gets a "#1"-style suffix. Use create_list instead to start an empty list from scratch.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_create_list`

Create List · Write

Creates a new, empty mailing list and returns its list_uid. To duplicate an existing list with its custom fields and segments use copy_list instead; to add contacts afterwards use create_subscriber or bulk_create_subscribers.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): List settings. Flat form: {"name": "Newsletter", "description": "Monthly news", "from_name": "Acme", "from_email": "news@acme.com", "reply_to": "support@acme.com", "subject": "Hello"}. The nested form {"general": {...}, "defaults": {...}, "notifications": {...}, "company": {...}} is also accepted.

Example input: `{}`

### `mailsenpaimcp_create_list_field`

Create List Field · Write

Adds a new custom field to a list (e.g. a "City" text field or a "Plan" dropdown) and returns it. Valid type identifiers come from list_list_field_types. Existing subscribers start with the new field empty.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Field definition, e.g. {"type": "text", "label": "City", "tag": "CITY", "required": "no"}. type: text, textarea, dropdown, multiselect, date, datetime, checkbox, consentcheckbox, phonenumber, email, url, rating or yearsrange. tag (UPPERCASE, max 32 characters) is derived from label if omitted. For dropdown/multiselect add "options": [{"name": "Gold", "value": "gold"}].
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_create_list_segment`

Create List Segment · Write

Creates a saved segment in a list from field conditions (and optional campaign open/click conditions) and returns its segment_uid. Get field_id values from list_list_fields and operators from list_segment_condition_operators.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Segment definition, e.g. {"name": "Rome customers", "operator_match": "all", "conditions": [{"field_id": 12, "operator": "contains", "value": "Rome"}]}. operator_match: all or any. Operator slugs: is, is-not, contains, not-contains, starts-with, ends-with, not-starts-with, not-ends-with, greater-than, less-than (or a numeric operator_id).
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_create_subscriber`

Create Subscriber · Write

Adds a new subscriber to a list and returns its subscriber_uid. Fails if the email is already in the list: use create_or_update_subscriber to add-or-update, or bulk_create_subscribers for many contacts at once. Depending on the list's opt-in setting the new subscriber may start as unconfirmed.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Subscriber data keyed by field tag; EMAIL is required, e.g. {"EMAIL": "jane@example.org", "FNAME": "Jane", "LNAME": "Doe"}. Optional: status, source, ip_address.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_create_template`

Create Template · Write

Saves a new reusable email template from HTML (or a ZIP archive) and returns its template_uid, which create_campaign can use. It does not create or send any campaign.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `template` (`object`, optional): Template object, e.g. {"name": "Welcome", "content": "<html>...</html>", "inline_css": "no"}. HTML is encoded automatically; a ZIP archive can be given as "archive": "base64:<data>".

Example input: `{}`

### `mailsenpaimcp_start_email_spam_test`

Start Email Spam Test · Write

Starts a free spam test and returns a unique test address (testspam+code@mailsenpai.com) and a test_token. The user must then send a real email to that address from the program they normally use (newsletter tool, CRM, website or app): this tool cannot send it for them. Then call get_email_spam_test_result with the test_token. Not read-only: it creates a test and MailSenpai emails the instructions to the account's address (or to email, when given; it must be a company address, not Gmail or similar). Ask the user before starting. Limits: 3 tests per address per day; the address expires after 24 hours. A test still waiting for the same address is reused.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): Optional company email that owns the test and receives the instructions. Omit to use the email of the connected MailSenpai account. Free and temporary mailboxes are rejected.
- `language` (`string`, optional): Language of the instructions email and of the result: en (default) or it. It cannot be changed later. One of: `en`, `it`.

Example input: `{}`

### `mailsenpaimcp_cancel_scheduled_campaign`

Cancel Scheduled Campaign · Destructive

Stops a scheduled campaign before it starts by moving it back to draft; nothing is deleted and it can be scheduled again later. For a campaign that is already sending use pause_unpause_campaign. Confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.

Example input: `{}`

### `mailsenpaimcp_confirm_subscriber`

Confirm Subscriber · Destructive

Sets a subscriber's status to confirmed by subscriber_uid: confirms an unconfirmed contact or re-subscribes one who unsubscribed, so they receive campaigns again. Do this only with the contact's consent and after the user confirms. Use confirm_subscriber_by_email if you only have the address.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Optional extra subscriber fields to save in the same call, keyed by field tag, e.g. {"FNAME": "Jane"}. Usually omitted.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `subscriber_uid` (`string`, optional): Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Example input: `{}`

### `mailsenpaimcp_confirm_subscriber_by_email`

Confirm Subscriber By Email · Destructive

Same as confirm_subscriber, but first finds the subscriber by email in the given list. Re-subscribing someone who opted out requires their consent, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Optional extra subscriber fields to save in the same call, keyed by field tag, e.g. {"FNAME": "Jane"}. Usually omitted.
- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_create_campaign`

Create Campaign · Destructive

Creates a new campaign, by default as a DRAFT that sends nothing. Needs list_uid, name, subject, from_name, from_email, reply_to, send_at and content (template_uid or template_content HTML). To duplicate a past campaign use copy_campaign; to create and schedule in one step use create_scheduled_campaign. status=pending-sending schedules real sending and requires confirm_send=true after explicit user approval.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `auto_plain_text` (`string`, optional): yes (default) to generate the plain-text version from the HTML. One of: `yes`, `no`. Default: `yes`.
- `campaign` (`object`, optional): Alternative to the flat fields: a complete campaign object, e.g. {"name": "October news", "list_uid": "ab123cd456ef7", "subject": "Hello", "from_name": "Acme", "from_email": "news@acme.com", "reply_to": "news@acme.com", "send_at": "2026-10-15 09:30:00", "template": {"template_uid": "..."}}. When it is not empty the flat fields are ignored.
- `confirm_send` (`boolean`, optional): Must be true only with status=pending-sending, after the user has explicitly approved sending to real recipients. Default: `false`.
- `cronjob` (`string`, optional): Advanced: cron expression to repeat a regular campaign, e.g. "0 9 * * 1" (Mondays 09:00). Usually omitted.
- `cronjob_enabled` (`string`, optional): Advanced: 1 to enable the cron repetition, 0 to disable.
- `email_stats` (`string`, optional): Optional email address that receives the statistics report when sending finishes.
- `from_email` (`string`, optional): Sender email address, e.g. "news@acme.com".
- `from_name` (`string`, optional): Sender name shown to recipients, e.g. "Acme".
- `inline_css` (`string`, optional): yes to convert <style> CSS into inline styles; default no. One of: `yes`, `no`. Default: `no`.
- `json_feed` (`string`, optional): Advanced: yes to enable JSON feed tags in the content. Usually omitted. One of: `yes`, `no`.
- `list_uid` (`string`, optional): Required (here or inside campaign): list_uid of the recipients' list, from list_lists.
- `name` (`string`, optional): Internal campaign name, e.g. "October newsletter".
- `plain_text` (`string`, optional): Optional plain-text version; normally generated automatically (auto_plain_text=yes).
- `plain_text_email` (`string`, optional): yes (default) to also send a plain-text version. One of: `yes`, `no`. Default: `yes`.
- `reply_to` (`string`, optional): Reply-to email address.
- `segment_uid` (`string`, optional): Optional: send only to this segment of the list (segment_uid from list_list_segments).
- `send_at` (`string`, optional): Send date and time "YYYY-MM-DD HH:MM:SS" in the account time zone, e.g. "2026-10-15 09:30:00". Required by the platform even for drafts; used only once the campaign is scheduled.
- `status` (`string`, optional): draft (default, nothing is sent) or pending-sending (schedules real sending at send_at; requires confirm_send=true). One of: `draft`, `pending-sending`. Default: `draft`.
- `subject` (`string`, optional): Email subject line.
- `template` (`object`, optional): Optional content: {"template_uid": "..."} to reuse a saved template, or {"content": "<html>...</html>"} for new HTML.
- `template_archive` (`string`, optional): Content option 3 (rare): ZIP archive with HTML and images, as "base64:<data>".
- `template_content` (`string`, optional): Content option 2: the email HTML, e.g. "<html><body>Hello [FNAME]</body></html>". Encoded automatically.
- `template_uid` (`string`, optional): Content option 1: template_uid of a saved template (from list_templates).
- `type` (`string`, optional): regular (default, one-off send) or autoresponder (triggered by subscriber events). One of: `regular`, `autoresponder`. Default: `regular`.
- `url_tracking` (`string`, optional): yes (default) to track link clicks, no to disable. One of: `yes`, `no`. Default: `yes`.
- `xml_feed` (`string`, optional): Advanced: yes to enable XML/RSS feed tags in the content. Usually omitted. One of: `yes`, `no`.

Example input: `{}`

### `mailsenpaimcp_create_or_update_subscriber`

Create Or Update Subscriber · Destructive

Upsert: looks up data.EMAIL in the list; if found it updates that subscriber, otherwise it creates a new one. Use it to sync contacts when you do not know whether they already exist. Existing values are overwritten, so confirm with the user before updating real contacts.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Subscriber data keyed by field tag; EMAIL is required, e.g. {"EMAIL": "jane@example.org", "FNAME": "Jane", "LNAME": "Doe"}. Optional: status, source, ip_address.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_create_scheduled_campaign`

Create Scheduled Campaign · Destructive

Creates a campaign and schedules it for real sending in one step (status pending-sending at campaign.send_at). To prepare a draft for review use create_campaign instead. Ask the user to approve list, content and send time, then call with confirm_send=true (plus approval_reference if the plan requires it).

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `campaign` (`object`, optional): Campaign object with list_uid, name, subject, from_name, from_email, reply_to and send_at ("YYYY-MM-DD HH:MM:SS", account time zone); give the content with "template" inside it or with the template parameter.
- `confirm_send` (`boolean`, optional): Must be true to send or schedule. Set it only after the user has explicitly approved sending to real recipients; otherwise the call is rejected. Default: `false`.
- `template` (`object`, optional): Optional content: {"template_uid": "..."} to reuse a saved template, or {"content": "<html>...</html>"} for new HTML.

Example input: `{}`

### `mailsenpaimcp_create_transactional_email`

Create Transactional Email · Destructive

Sends one transactional email to a single recipient, queued for immediate delivery or for send_at. It is a real send: show the user the recipient and content and call with confirm_send=true only after approval. To email a whole list use a campaign instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `confirm_send` (`boolean`, optional): Must be true to send. Set it only after the user has approved the recipient and the content; otherwise the call is rejected. Default: `false`.
- `email` (`object`, optional): Email object, e.g. {"to_name": "Jane", "to_email": "jane@example.org", "from_name": "Acme", "from_email": "noreply@acme.com", "reply_to_email": "help@acme.com", "subject": "Your receipt", "body": "<base64 HTML>", "send_at": "YYYY-MM-DD HH:MM:SS"}. body (and optional plain_text) must be base64-encoded; to_email, to_name, from_name, subject and body are required; send_at defaults to now. Optional "attachments": [{"name": "a.pdf", "type": "application/pdf", "data": "<base64>"}].

Example input: `{}`

### `mailsenpaimcp_delete_campaign`

Delete Campaign · Destructive

Permanently deletes a campaign and its statistics; this cannot be undone. To stop a campaign but keep it use cancel_scheduled_campaign or pause_unpause_campaign. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.
- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.

Example input: `{}`

### `mailsenpaimcp_delete_list`

Delete List · Destructive

Permanently deletes a mailing list together with all its subscribers, custom fields and segments; this cannot be undone. Ask the user for explicit confirmation, then call with confirm_delete=true. Only available if the plan allows deletions.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_delete_list_field`

Delete List Field · Destructive

Permanently deletes a custom field from a list, together with the values stored in it for every subscriber; this cannot be undone. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `field_id` (`string`, optional): Numeric ID of the custom field (field_id), e.g. 12. Find it with list_list_fields.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_delete_list_segment`

Delete List Segment · Destructive

Permanently deletes a saved segment; the subscribers themselves are kept. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `segment_uid` (`string`, optional): Unique ID of the segment (segment_uid). Find it with list_list_segments.

Example input: `{}`

### `mailsenpaimcp_delete_subscriber`

Delete Subscriber · Destructive

Permanently deletes a subscriber (by subscriber_uid) and its history from a list; this cannot be undone. To stop emails while keeping the record use unsubscribe_subscriber instead. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `subscriber_uid` (`string`, optional): Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Example input: `{}`

### `mailsenpaimcp_delete_subscriber_by_email`

Delete Subscriber By Email · Destructive

Same as delete_subscriber, but first finds the address in the given list. Permanent; for a simple opt-out use unsubscribe_subscriber_by_email. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_delete_template`

Delete Template · Destructive

Permanently deletes a saved template; campaigns that already used it keep their content. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `template_uid` (`string`, optional): Unique ID of the saved email template (template_uid). Find it with list_templates or search_templates.

Example input: `{}`

### `mailsenpaimcp_delete_transactional_email`

Delete Transactional Email · Destructive

Permanently deletes a transactional email record by email_uid; this cannot be undone. Ask the user for explicit confirmation, then call with confirm_delete=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `confirm_delete` (`boolean`, optional): Must be true to delete. Set it only after the user has explicitly confirmed this permanent deletion; otherwise the call is rejected. Default: `false`.
- `email_uid` (`string`, optional): Unique ID of the transactional email (email_uid). Find it with list_transactional_emails.

Example input: `{}`

### `mailsenpaimcp_mark_campaign_as_sent`

Mark Campaign As Sent · Destructive

Marks a campaign as sent, which permanently stops any remaining delivery; it cannot be resumed afterwards. Use it only to close a stuck or abandoned campaign, after explicit user confirmation, with confirm_send=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.
- `confirm_send` (`boolean`, optional): Must be true to send or schedule. Set it only after the user has explicitly approved sending to real recipients; otherwise the call is rejected. Default: `false`.

Example input: `{}`

### `mailsenpaimcp_pause_unpause_campaign`

Pause Unpause Campaign · Destructive

Toggles a campaign between sending and paused: a sending campaign is paused, a paused campaign RESUMES sending. Check the current status with get_campaign first and confirm with the user, because resuming restarts delivery.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.

Example input: `{}`

### `mailsenpaimcp_reschedule_campaign`

Reschedule Campaign · Destructive

Changes the send date and time of a campaign that is already scheduled (it stays pending-sending). Use schedule_campaign_send for a draft that is not scheduled yet. Requires confirm_send=true after the user approves the new time.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.
- `confirm_send` (`boolean`, optional): Must be true to send or schedule. Set it only after the user has explicitly approved sending to real recipients; otherwise the call is rejected. Default: `false`.
- `send_at` (`string`, optional): Send date and time as "YYYY-MM-DD HH:MM:SS" in the account time zone, e.g. "2026-10-15 09:30:00".

Example input: `{}`

### `mailsenpaimcp_schedule_campaign_send`

Schedule Campaign Send · Destructive

Schedules an existing draft campaign for real sending at send_at (status becomes pending-sending). Use reschedule_campaign to move an already scheduled campaign and cancel_scheduled_campaign to stop it before it starts. Ask the user to approve, then call with confirm_send=true.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.
- `confirm_send` (`boolean`, optional): Must be true to send or schedule. Set it only after the user has explicitly approved sending to real recipients; otherwise the call is rejected. Default: `false`.
- `send_at` (`string`, optional): Send date and time as "YYYY-MM-DD HH:MM:SS" in the account time zone, e.g. "2026-10-15 09:30:00".

Example input: `{}`

### `mailsenpaimcp_set_subscriber_status`

Set Subscriber Status · Destructive

Sets any status on a subscriber identified by subscriber_uid: confirmed, unconfirmed, unsubscribed, blacklisted, unapproved, disabled or moved. For the common cases prefer confirm_subscriber or unsubscribe_subscriber. It changes who receives emails, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Optional extra subscriber fields to save in the same call, keyed by field tag, e.g. {"FNAME": "Jane"}. Usually omitted.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `status` (`string`, optional): Subscriber status: confirmed, unconfirmed, unsubscribed, blacklisted, unapproved, disabled or moved. One of: `confirmed`, `unconfirmed`, `unsubscribed`, `blacklisted`, `unapproved`, `disabled`, `moved`.
- `subscriber_uid` (`string`, optional): Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Example input: `{}`

### `mailsenpaimcp_set_subscriber_status_by_email`

Set Subscriber Status By Email · Destructive

Same as set_subscriber_status, but first finds the subscriber by email in the given list. It changes who receives emails, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Optional extra subscriber fields to save in the same call, keyed by field tag, e.g. {"FNAME": "Jane"}. Usually omitted.
- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `status` (`string`, optional): Subscriber status: confirmed, unconfirmed, unsubscribed, blacklisted, unapproved, disabled or moved. One of: `confirmed`, `unconfirmed`, `unsubscribed`, `blacklisted`, `unapproved`, `disabled`, `moved`.

Example input: `{}`

### `mailsenpaimcp_unsubscribe_subscriber`

Unsubscribe Subscriber · Destructive

Unsubscribes one subscriber (by subscriber_uid) from one list: the record and its history are kept with status unsubscribed and it stops receiving campaigns; reversible with confirm_subscriber. Use delete_subscriber only to erase the record completely. Confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `subscriber_uid` (`string`, optional): Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Example input: `{}`

### `mailsenpaimcp_unsubscribe_subscriber_by_email`

Unsubscribe Subscriber By Email · Destructive

Same as unsubscribe_subscriber, but finds the address in ONE given list. To opt an address out of every list at once use unsubscribe_subscriber_from_all_lists_by_email. Confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_unsubscribe_subscriber_from_all_lists_by_email`

Unsubscribe Subscriber From All Lists By Email · Destructive

Unsubscribes an email address from ALL lists of the account in one call; the records are kept with status unsubscribed. Use it for global opt-out requests; use unsubscribe_subscriber_by_email for a single list. Confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".

Example input: `{}`

### `mailsenpaimcp_update_campaign`

Update Campaign · Destructive

Edits an existing campaign by campaign_uid (name, subject, sender, list or segment, content, send time); normally only drafts and paused campaigns can be changed. Setting status=pending-sending or a send_at schedules real sending and needs confirm_send=true after explicit user approval; confirm other changes with the user too.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `approval_reference` (`string`, optional): Approval reference (free text, e.g. an approval ticket ID). Needed only when the plan requires approval before sending; see get_my_mailsenpai_capabilities.
- `campaign` (`object`, optional): Campaign fields to change, e.g. {"subject": "New subject"} or {"send_at": "2026-10-15 09:30:00"}. Setting status pending-sending or send_at requires confirm_send=true.
- `campaign_uid` (`string`, optional): Unique ID of the campaign (campaign_uid), a 13-character code. Find it with list_campaigns.
- `confirm_send` (`boolean`, optional): Must be true to send or schedule. Set it only after the user has explicitly approved sending to real recipients; otherwise the call is rejected. Default: `false`.
- `template` (`object`, optional): Optional content: {"template_uid": "..."} to reuse a saved template, or {"content": "<html>...</html>"} for new HTML.

Example input: `{}`

### `mailsenpaimcp_update_list`

Update List · Destructive

Changes the settings of an existing list (name, description, default sender, notifications, company) identified by list_uid. Takes the same data format as create_list; subscribers are not touched. It overwrites the current values, so confirm the changes with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Settings to change, same format as create_list, e.g. {"name": "Newsletter IT", "from_name": "Acme Italia"}.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_update_list_field`

Update List Field · Destructive

Changes an existing custom field (label, tag, type, required flag, visibility, options) by field_id. Changing the tag or type can break templates and segments that use the field, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Field properties to set, same format as create_list_field, e.g. {"label": "Town", "required": "yes"}.
- `field_id` (`string`, optional): Numeric ID of the custom field (field_id), e.g. 12. Find it with list_list_fields.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_update_list_segment`

Update List Segment · Destructive

Replaces the name, match mode and conditions of an existing segment by segment_uid. Campaigns that target the segment will use the new conditions, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): New segment definition, same format as create_list_segment.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `segment_uid` (`string`, optional): Unique ID of the segment (segment_uid). Find it with list_list_segments.

Example input: `{}`

### `mailsenpaimcp_update_subscriber`

Update Subscriber · Destructive

Updates the custom field values (and optionally the status) of an existing subscriber identified by subscriber_uid. Use update_subscriber_by_email if you only have the address. It overwrites the values you pass, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Fields to change keyed by field tag, e.g. {"FNAME": "Janet", "CITY": "Milan"}. To change only the status prefer the set_subscriber_status tools.
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
- `subscriber_uid` (`string`, optional): Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Example input: `{}`

### `mailsenpaimcp_update_subscriber_by_email`

Update Subscriber By Email · Destructive

Same as update_subscriber, but first finds the subscriber by email address in the given list; returns an error if the address is not in that list. It overwrites the values you pass, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `data` (`object`, optional): Fields to change keyed by field tag, e.g. {"FNAME": "Janet", "CITY": "Milan"}. To change only the status prefer the set_subscriber_status tools.
- `email` (`string`, optional): Email address of the subscriber, e.g. "jane@example.org".
- `list_uid` (`string`, optional): Unique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.

Example input: `{}`

### `mailsenpaimcp_update_template`

Update Template · Destructive

Replaces the name and/or HTML content of an existing template by template_uid. Campaigns already created from it keep their own copy of the content. It overwrites the template, so confirm with the user first.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `template` (`object`, optional): Template fields to replace, same format as create_template, e.g. {"name": "Welcome v2", "content": "<html>...</html>"}.
- `template_uid` (`string`, optional): Unique ID of the saved email template (template_uid). Find it with list_templates or search_templates.

Example input: `{}`

## Related

Other Marketing connectors ([all 190](/agentkit/connectors/?category=marketing)):

- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Mailchimp](/agentkit/connectors/mailchimp/): Scalekit connector, OAuth, 73 tools
- [Twitter / X](/agentkit/connectors/twitteroauth/): Scalekit connector, OAuth, 92 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
