SMTP
Send transactional email through your own SMTP server (Gmail, Outlook, custom mailserver). Bring your own credentials — full control over deliverability and sender reputation.
Endpoints (3)
Queue an email for asynchronous delivery via SMTP. Returns immediately; worker picks up the job from the smtp queue. Use this for normal transactional sends (form notifications, confirmations).
| Field | Type | Required | Description |
|---|---|---|---|
to |
string|array | ✓ Yes | Recipient email address, or array of addresses (max 50) |
subject |
string | ✓ Yes | Email subject line |
html |
string | No | HTML body content. Provide either html, text, or both. |
text |
string | No | Plain text body (fallback for clients that do not render HTML) |
reply_to |
string | No | Reply-to address (optional — defaults to from address) |
Send multiple emails in a single TCP connection (keep-alive). Synchronous — returns per-email status. Use for newsletters or batched notifications. Max 50 emails per call.
| Field | Type | Required | Description |
|---|---|---|---|
emails |
array | ✓ Yes | Array of email objects, each with: to (string|array), subject (string), html (string), text (string), reply_to (string) |
Validate SMTP credentials by performing the full TCP + TLS + AUTH handshake against the configured server. No email is sent. Returns duration_ms on success, mapped error message on failure.
No input parameters required.
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| send-email | smtp_send_email |
| send-emails | smtp_send_emails |
| test-connection | smtp_test_connection |