MCP recipes

Common transactional email tasks expressed as prompts for Claude or any MCP-compatible AI assistant. Copy, adapt, and drop into your workflow.

---

Send a welcome email

Prompt:

Send a welcome email to new.user@example.com. Their name is Priya and they signed up for MyApp. Use the Brixus365 welcome template.

What happens:

1. Claude calls brixus_list_starter_templates to confirm welcome is available.
2. Claude calls brixus_send_email with starter_template: "welcome", variables: { name: "Priya", app_name: "MyApp" }, and to: "new.user@example.com".
3. Returns the messageId and status: "queued".

Direct tool call (for scripting):

{
  "tool": "brixus_send_email",
  "to": "new.user@example.com",
  "starter_template": "welcome",
  "variables": {
    "name": "Priya",
    "app_name": "MyApp"
  }
}

---

Send an OTP

Prompt:

Send a one-time password to user@example.com. The OTP is 847291 and it expires in 10 minutes.

Direct tool call:

{
  "tool": "brixus_send_email",
  "to": "user@example.com",
  "starter_template": "otp",
  "variables": {
    "otp_code": "847291",
    "expiry_minutes": "10"
  }
}

---

Send with custom variables

Prompt:

Send an order receipt to customer@example.com. Order number is #1042, total is ₹2,499, and the item is “Pro Plan — Annual”. Use the receipt template.

Direct tool call:

{
  "tool": "brixus_send_email",
  "to": "customer@example.com",
  "starter_template": "receipt",
  "variables": {
    "order_number": "1042",
    "order_total": "₹2,499",
    "item_name": "Pro Plan — Annual"
  }
}

---

Preview before sending

Prompt:

Show me how the Brixus365 welcome template looks for a user named Rohan signing up for BuildFast. Don’t send it yet.

What happens:

1. Claude calls brixus_preview_starter_template with slug: "welcome" and variables: { name: "Rohan", app_name: "BuildFast" }.
2. Returns the subject line and rendered HTML — no email sent.

Use this to confirm your variable values render correctly before triggering the actual send.

---

Find the right template

Prompt:

What Brixus365 starter templates are available? I need something for a password reset.

What happens:

1. Claude calls brixus_list_starter_templates.
2. Returns all templates with slugs, descriptions, and expected variables.
3. Claude identifies password_reset as the right fit and shows the required variables (reset_url, expiry_minutes).

You can then immediately follow up: “Send the password reset template to user@example.com with reset_url https://app.example.com/reset/abc123 and expiry_minutes 30.”

---

Safe retry pattern

Prompt:

Send a password reset email to user@example.com with reset URL https://app.example.com/reset/xyz789. This is a retry — make sure it doesn’t send twice.

Claude will automatically include an Idempotency-Key derived from the operation context, so the email is only sent once even if the tool is called multiple times with the same intent.

For scripting where you control the key explicitly:

{
  "tool": "brixus_send_email",
  "to": "user@example.com",
  "starter_template": "password_reset",
  "variables": {
    "reset_url": "https://app.example.com/reset/xyz789",
    "expiry_minutes": "30"
  }
}

Add Idempotency-Key: password-reset-{user_id}-{request_id} in the HTTP header when calling via API directly. See Idempotency for the full pattern.

---

Debug why an email didn’t arrive

Prompt:

The welcome email I sent to user@example.com 20 minutes ago hasn’t arrived. Can you check if it was sent and what status it has?

What happens:

1. Claude reviews the messageId from the earlier send (if in context).
2. Points you to Connect → Transactional → Send History and the Audit Trail drawer for that message.
3. The status and event timeline will show whether the email reached the recipient, bounced, or is still pending.

Common causes of non-delivery:

Status	Likely cause	Fix
Sent (no Delivered)	Recipient’s server hasn’t confirmed acceptance yet — normal for a few minutes. If it stays Sent for over an hour, check the address.	Wait, then check the address for typos.
Bounced	Address doesn’t exist or rejected the email.	Verify the address. The bounce is now suppressed — future sends to this address will be skipped.
Failed	Internal error during dispatch.	Retry. If it persists, contact support with the messageId.
Pending (old)	Stuck in the send queue.	Contact support with the messageId and timestamp.

---

What’s next

You want to…	Go to
Set up the MCP server in Claude Desktop	MCP Quickstart
See the complete tool reference	Tools Reference
Use idempotency keys to prevent duplicates	Idempotency
See all starter templates and their variables	Starter templates