Integration

turboSMTP integration

turboSMTP is a transactional and marketing email relay. Send emails (HTML or text, attachments, cc/bcc, custom headers), read delivery analytics per message, manage the suppression list (bounces, unsubscribes, complaints), validate single addresses or uploaded lists with the Email Validator, configure alert notifications, and manage reseller sub-accounts. Login, logout, password, consumer-key management and sub-account login routes are not exposed, nor are CSV exports, the agency logo routes or buying Email Validator credits. Authentication is a permanent consumer key and consumer secret pair, created in the turboSMTP dashboard, sent as the consumerKey and consumerSecret headers.

Connect turboSMTP How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in turboSMTP.Built from the 35 turboSMTP tools below, on the connection you add once.

What you can do with turboSMTP

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.

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

Alert, 5 operations

create_alertCreate alertPOSTCreates an alert notification that emails the given address when account usage reaches percentage (0 to 100). Returns the alert with its id.
delete_alertDelete alertDELETEDeletes an alert notification.
get_alertGet alertGETReturns one alert notification: id, the email it notifies and the usage percentage that triggers it.
list_alertsList alertsGETLists alert notifications: each one emails an address when the account's usage reaches a percentage. Returns count and results with id, email and percentage.
update_alertUpdate alertPATCHUpdates an alert notification. email is always required: read it first with get_alert and send it back if unchanged. Leave percentage out to keep it.

Suppression, 5 operations

bulk_delete_suppressionsBulk delete suppressionsPOSTRemoves the given addresses from the suppression list, so turboSMTP sends to them again. Returns success. Cannot be undone.
delete_suppressions_by_filterDelete suppressions by filterPOSTRemoves every suppression added between from and to that matches filter, filter_by and restrict (none set: the whole date range), so turboSMTP sends to them again. Cannot be undone. Preview with filter_suppressions first.
filter_suppressionsFilter suppressionsPOSTLists suppressed addresses like list_suppressions, with the filters in the body and extra include or exclude restrictions on sender, recipient, reason or subject. Paged with page and limit. Changes nothing.
import_suppressionsImport suppressionsPOSTAdds email addresses to the suppression list so turboSMTP stops sending to them; returns the valid and invalid addresses. type must be manual. Importing a CSV file is not offered here.
list_suppressionsList suppressionsGETLists suppressed addresses (bounces, spam reports, unsubscribes, manual and failed validation) added between from and to (YYYY-MM-DD), with date, sender, source, subject, recipient and reason. Paged with page and limit.

Validation list, 5 operations

delete_email_validation_listDelete email validation listDELETEDeletes an Email Validator list and its results. This cannot be undone.
get_email_validation_listGet email validation listGETReturns one Email Validator list: file name, creation time, whether processing finished, progress percentage, total and processed email counts, and the count per validation status.
list_email_validation_listsList email validation listsGETLists Email Validator lists uploaded between from and to (YYYY-MM-DD): id, file name, whether processing finished, progress percentage, email counts and a per-status summary. Paged with page and limit.
upload_email_validation_fileUpload email validation filePOSTUploads a CSV or TXT file of email addresses (one per line) as a new Email Validator list and returns its id and email count. Validation does not start until validate_email_validation_list is called.
validate_email_validation_listValidate email validation listPOSTStarts validating an uploaded Email Validator list. Uses Email Validator credits (see get_email_validation_subscription). Follow progress with get_email_validation_list, then read results with list_validated_emails.

Subaccount, 4 operations

create_subaccountCreate subaccountPOSTCreates a reseller sub-account with its owner, sending IP, address and password, and returns the new sub-account with its id. policy_agree must be true. Reseller (agency) accounts only.
get_subaccountGet subaccountGETReturns one sub-account: email, sending IP, active flag, owner name, address, company, phone and website.
list_subaccountsList subaccountsGETLists your reseller sub-accounts with email, IP, active flag, sending limit and usage, plan expiry and last use, paged with page and limit. Filter by email, active status or IP.
update_subaccountUpdate subaccountPATCHUpdates a sub-account. ip, first_name, last_name and policy_agree (true) are always required: read them first with get_subaccount and send them back with your change. Other fields: leave out to keep.

Agency settings, 2 operations

get_agency_settingsGet agency settingsGETReturns the agency (reseller) settings shown to sub-accounts: logo URL, agency name, website and email footer.
update_agency_settingsUpdate agency settingsPATCHUpdates the agency (reseller) name, website or email footer shown to sub-accounts. Leave a field out to keep its current value.

Email, 2 operations

send_emailSend emailPOSTSends an email now through the global sending host and returns message OK and its mid. from and to are required; the body goes in content (text), html_content or mime_raw. Total size with attachments under 24MB.
send_email_euSend email euPOSTSends an email now through turboSMTP's EU sending infrastructure (EU data residency), otherwise identical to send_email. from and to are required; the body goes in content, html_content or mime_raw.

Sent email, 2 operations

get_sent_emailGet sent emailGETReturns one sent email by its id (the id field of a list_sent_emails row): sender, recipient, subject, send time, delivery status, domains, campaign id and delivery error.
list_sent_emailsList sent emailsGETLists sent emails between from and to (YYYY-MM-DD), one row per message with sender, recipient, subject, send time, status and error, paged with page and limit. Filter by status[] or search text with filter and filter_by[].

Validated email, 2 operations

get_validated_emailGet validated emailGETReturns the validation result of one address in an Email Validator list: status, sub-status, typo suggestion, domain, domain age, SMTP provider and MX record.
list_validated_emailsList validated emailsGETLists the validated addresses of an Email Validator list with status, sub-status, domain, MX and free-provider flags, paged with page and limit. Run validate_email_validation_list on the list first.

Account email, 1 operation

check_account_email_existsCheck account email existsGETChecks whether an email address is already used by a turboSMTP account, for example before create_subaccount. Returns result true or false.

Country, 1 operation

get_countriesGet countriesGETLists every country with its ISO code, currency, flag emoji, name and phone code. Needs no credential. Use the iso_code with get_states_by_country.

Email address, 1 operation

validate_emailValidate emailPOSTValidates one email address in real time and returns its status (valid, invalid, catch-all and so on), sub-status, typo suggestion, domain and MX data. Uses Email Validator credits.

State, 1 operation

get_states_by_countryGet states by countryGETLists the states or regions of a country given its two-letter ISO code (from get_countries): name, ISO code, country code and type. Needs no credential.

Subaccount plan, 1 operation

get_subaccount_active_planGet subaccount active planGETReturns the active plan of a sub-account: sending limit and interval (daily, monthly or yearly), emails sent in the current period, plan expiry and whether it has expired.

Subaccount sending limit, 1 operation

update_subaccount_sending_limitUpdate subaccount sending limitPOSTSets how many emails a sub-account may send per plan interval (-1 for no limit) and returns its updated plan.

Subaccount status, 1 operation

update_subaccount_statusUpdate subaccount statusPOSTActivates or deactivates a sub-account: users cannot log in to an inactive one. Sending also needs an active subscription. Returns the updated sub-account plan.

Validation balance, 1 operation

get_email_validation_subscriptionGet email validation subscriptionGETReturns the Email Validator balance: free credits allocated, used and remaining, the free credit period dates, the remaining paid balance and its currency, and when credits were last used.

Use turboSMTP from Claude Code, Cursor or Codex

Connect turboSMTP in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its turboSMTP 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 turboSMTP

Create your workspace
Sign up free. Nothing to install.
Connect turboSMTP once
Add your turboSMTP 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.