Workflows

Example workflows for using Emailens MCP tools with Claude and other AI assistants.

Overview

Once the Emailens MCP server is connected, your AI assistant can call the email analysis tools directly. This enables conversational email QA — paste your HTML, ask questions, and get structured results.

Example workflows

Analyze and fix

You: "Analyze this email and fix any Outlook compatibility issues"

AI calls analyze_email → finds border-radius and flexbox warnings
AI calls fix_email → generates fix prompt with table-based layout changes
AI applies the fixes to your code

Iterative improvement with diff

You: "Analyze this email template"
AI calls analyze_email → reports a score of 72/100

You: "Fix the top issues"
AI applies the suggested code fixes

You: "Did the fixes help? Compare the original and fixed versions"
AI calls diff_emails → shows score improved from 72 to 94
→ 12 clients improved, 0 regressed, 3 unchanged

Full quality audit

You: "Run a full audit on this email — check everything"
AI calls audit_email → returns compatibility scores, spam analysis,
link validation, accessibility issues, image analysis, inbox preview,
size check, and template variable detection

Deliverability check

You: "Check if company.com has proper email authentication"
AI calls check_deliverability → reports SPF, DKIM, DMARC, MX, BIMI status
→ "SPF: pass, DKIM: warn (no selector found), DMARC: pass, Score: 75/100"

Screenshots for stakeholders

You: "Take screenshots of this email across all clients"
AI calls capture_screenshots → returns CDN-hosted screenshot URLs
→ "Screenshots captured for 15 clients. View at emailens.dev/preview/abc123"

You: "Create a shareable link so my designer can see the results"
AI calls share_preview → returns a public URL
→ "Share link: emailens.dev/share/xyz789 (expires in 7 days)"

Tips

Use analyze for quick checks — analyze_email is fastest when you only need CSS compatibility scores
Use audit for thorough checks — audit_email covers spam, links, accessibility, images, size, and more
Iterate with diff — after fixing issues, use diff_emails to verify improvements across all 15 clients
Be specific about clients — pass clients: ["gmail-web", "outlook-windows"] to focus on specific clients
Check deliverability early — check_deliverability catches DNS issues before you send

Tool availability

The MCP server uses the same @emailens/engine as the web app and REST API. Local tool results are identical. Hosted tools (screenshots, sharing) require an API key — see Setup.

On this page