Integration

SMTP Senpai integration

SMTP Senpai is the transactional email relay of MailSenpai. Send transactional emails (up to 500 recipients per call, each with its own copy, with attachments and custom headers), read the delivery event log and the sending statistics, manage the suppression list, check the monthly volume left and configure the account's event webhook. Left out: the public website-form endpoint (it takes no key and is meant for a browser form), the drop-in endpoints that mimic other email APIs, and rotating the webhook signing secret. Authentication is the API key (it starts with msp_) shown in the MailSenpai customer area, SMTP Senpai page, sent as a Bearer token.

Connect SMTP Senpai How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SMTP Senpai.Built from the 10 SMTP Senpai tools below, on the connection you add once.

What you can do with SMTP Senpai

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Suppression, 3 operations

add_suppressionAdd suppressionPOSTAgents: ask firstAdds an address, or a whole domain (@domain.com or domain.com), to the suppression list: no email is sent to it again until it is removed. Answers gia_presente true when it was already there.
list_suppressionsList suppressionsGETAgents: ask firstLists the addresses and whole domains (written @domain.com) that are no longer emailed, with why (bounce, complaint or manuale), a note and the date. Personal data: email addresses.
remove_suppressionRemove suppressionPOSTAgents: ask firstRemoves from the suppression list an entry you added yourself, so it can be emailed again. Entries added by a bounce or a spam report are refused (409; ask for a review in the customer area); an entry not on the list answers 404.

Webhook, 3 operations

get_webhookGet webhookGETAgents: ask firstReturns the account's event webhook: its address, the event types it receives, whether it is on, the event types it can receive and the deliveries of the last 24 hours (delivered, waiting, failed).
send_test_webhook_eventSend test webhook eventPOSTAgents: ask firstPosts a test event (with test true) to the account's webhook address right away and returns what that server answered: its HTTP code and any error.
set_webhookSet webhookPOSTAgents: ask firstSets the account's single event webhook: its https address, the event types sent to it, or turns it on or off. Changes where real events are posted. The signing secret in the answer is withheld (see details).

Account, 1 operation

get_account_statusGet account statusGETAgents: ask firstReturns the account status (pending or active), the SMTP connection details (server, ports, username; never the password), this month's volume (included, used, left, hourly pace), whether open and click tracking is on, and the suppression list size.

Email, 1 operation

send_emailSend emailPOSTAgents: ask firstSends a real email: each recipient in to (1 to 500) gets its own copy. Up to 50 go out at once, 51 to 500 are queued. Counts against the plan's monthly volume. The sender must be on a domain verified in the account.

Event, 1 operation

list_eventsList eventsGETAgents: ask firstReads the delivery log (personal data: recipient addresses). Without after: the latest events, newest first. With after: the events after that event_id, oldest first, plus prossimo to pass as after next time.

Statistics, 1 operation

get_sending_statisticsGet sending statisticsGETAgents: ask firstReturns sending totals over the last N days (sent, delivered, bounce, defer, complaint, delivery, bounce and complaint rates; opens and clicks only with tracking on) and a day-by-day breakdown of at most the last 30 days.

Use SMTP Senpai from Claude Code, Cursor or Codex

Connect SMTP Senpai in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SMTP Senpai operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SMTP Senpai

Create your workspace
Sign up free. Nothing to install.
Connect SMTP Senpai once
Add your SMTP Senpai connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.