MailBluster

@MailBluster list all custom fields we've defined for leads, then show me which ones are required vs optional

Retrieved 8 custom fields from your MailBluster account. Required fields: 'company_name' (text), 'industry' (dropdown with 5 options). Optional fields: 'phone_number' (text), 'website_url' (URL), 'employee_count' (number), 'last_contact_date' (date), 'lead_source' (dropdown with 7 options), 'notes' (long text). All fields are available for use when creating new leads via the API or import.

This example demonstrates the read-only list operation that helps teams audit their lead schema before bulk imports or automation setup. Requires a valid API key with read access to custom fields. The MCP returns field metadata but not the values stored in individual lead records.

@MailBluster create a new lead for emma.chen@techcorp.io with company name 'TechCorp' and industry 'SaaS', mark lead source as 'webinar'

Lead created successfully. Email: emma.chen@techcorp.io, ID: lead_9x4k2m. Custom fields populated: company_name='TechCorp', industry='SaaS', lead_source='webinar'. The lead is now active in your MailBluster account and will be included in any campaigns targeting the 'SaaS' industry segment. No email was sent as part of this creation—this is a CRM record only.

This write operation adds a contact to your MailBluster database with structured metadata. The prompt must include the required 'email' field; other fields are optional but useful for segmentation. Be aware this creates a billable contact in your MailBluster plan, and the lead will immediately appear in your dashboard and be eligible for campaigns.

@MailBluster pull the last 5 orders we've logged, then draft a summary email highlighting our top-selling product category this month

Retrieved 5 recent orders (IDs: ord_a1b2, ord_c3d4, ord_e5f6, ord_g7h8, ord_i9j0). Analysis: 3 of 5 orders contained products in the 'Enterprise Software' category, totaling $47,200 in revenue. Draft summary: 'Hi team—Enterprise Software dominated this month with 60% of recent orders and nearly $50K in sales. Our top SKU was 'Analytics Pro Annual' (2 units). Consider featuring this category in next week's campaign.' This draft is ready for your review before sending.

This synthesis example combines MailBluster's order retrieval with AI reasoning to surface business insights. The MCP fetches raw order data (product IDs, amounts, timestamps), and the AI interprets patterns. Useful for quick reporting, but note that 'last 5 orders' is a small sample—production analysis should use larger datasets or date ranges for statistical validity.

When MailBluster wins for transactional email follow-up

A 6-person DTC brand runs Shopify and sends weekly newsletters through MailBluster. They want their AI workspace to pull order data and create targeted follow-up campaigns—cart abandonment for leads who didn't convert, post-purchase upsells for recent buyers. This MCP handles it: the Create Order and Create Lead tools let the AI log transactions and contacts in real-time, while Get Order and List Fields pull segmentation data for campaign planning. The threshold: if you're sending more than 10k emails per month or need advanced automation (drip sequences, A/B testing), MailBluster's native integrations get clunky and you'll want a dedicated ESP like Klaviyo. Below that volume, this MCP keeps your email ops inside the same workspace where you're already planning product launches and reviewing customer feedback.

This MCP speeds up launch-day email coordination

A 3-person SaaS team is launching a new pricing tier next Tuesday. They're using MailBluster to announce it to their 2,000-subscriber list, and they need the AI to draft the email, update the product catalog with the new tier details, and create a lead magnet for trial signups—all in one session. The Create Product and Get Product tools let the AI confirm what's already in MailBluster, add the new tier, and reference it in the email copy without leaving Switchy. The Delete Product tool cleans up test entries from rehearsal runs. This works because the team is small and the catalog is under 50 products. If you're managing hundreds of SKUs or need real-time inventory sync, this MCP doesn't replace a proper PIM—it's for teams where the product person and the email person are the same person.

When this MCP handles event follow-up in the field

A 4-person B2B consultancy collects 30-40 business cards at a conference. Back at the hotel, they want the AI to parse the cards (via OCR or manual entry), create MailBluster leads with custom fields for booth conversation notes, and draft personalized follow-up emails for Monday morning. The Create MailBluster Lead tool takes the email and optional data (company, role, pain point discussed) and logs it immediately. List Fields confirms which custom attributes are available for segmentation. This scenario works because the volume is manageable and the team wants one workspace for both lead capture and email drafting. If you're collecting 500+ leads per event or need CRM-level pipeline tracking, MailBluster isn't built for that—you'd route leads to HubSpot or Salesforce instead. For small-batch, high-touch follow-up, this MCP keeps the workflow tight.