Emailens MCP
An MCP server for analyzing, previewing, fixing, and testing email templates across 21 email clients, with optional hosted features and a test-inbox sandbox.
Preview emails (
preview_email): transform HTML for 21 clients, CSS analysis, scores, dark-mode simulation, inbox preview, size checks.Analyze CSS compatibility (
analyze_email): per-client scores with one finding per problem, source positions (loc,alsoAtLines), optional client filtering and detail levels.Audit quality (
audit_email): spam scoring, link validation, accessibility, images, Gmail clipping size, template variables, overflow, contrast (dark/mobile), design consistency, VML faults, style survival, targeting, plusdesignRemovalsvs. a previous version.Generate fixes (
fix_email): structured markdown fix prompts for CSS/structural issues.Diff versions (
diff_emails): score changes, fixed and newly introduced issues per client.Check design fidelity (
check_design): renders in a real browser and compares layouts per client (needsplaywright-core/Chromium or Browserless, optionalsharpfor pixel diffs).List clients (
list_clients): IDs, names, engines, dark-mode support for all 21 clients.Check deliverability (
check_deliverability): SPF, DKIM, DMARC, MX, BIMI with a score (DNS only, no key).Capture screenshots (
capture_screenshots): real browser screenshots in light/dark across clients, CDN-hosted (API key required).Share previews (
share_preview): shareable analysis links (API key, Dev plan).Sandbox testing (
sandbox_get_inbox,sandbox_wait_for_email,sandbox_list_messages,sandbox_get_message): get a test address, wait for incoming mail, extract OTPs/action links, inspect captured messages (API key required).Template formats supported: HTML, MJML, Maizzle (incl. Vue SFC), React Email (
jsx), compiled before analysis.
Provides compatibility analysis and previews for email clients on the Android platform, including Gmail and Outlook Android.
Analyzes and previews email rendering for Apple Mail across macOS and iOS platforms.
Performs deep CSS compatibility analysis for HTML emails, identifying warnings and scores for 15 different email clients.
Offers comprehensive tools to analyze, preview, and fix email rendering issues specifically for Gmail across web, Android, and iOS.
Supports email compatibility analysis and previewing for the HEY Mail service.
Facilitates email compatibility testing and previewing for mobile clients on iOS, such as Apple Mail, Gmail, and Outlook.
Enables compatibility analysis and previews for Apple Mail on the macOS operating system.
Outputs structured fix instructions and audit results in Markdown format for easy application by AI or developers.
Provides compatibility analysis and rendering previews for Samsung Mail.
Offers email rendering analysis and compatibility previews for the Thunderbird email client.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Email rendering analysis for AI assistants
MCP server for email compatibility analysis. Analyze, preview, diff, and fix emails across 21 email clients, plus capture real screenshots and create shareable links with an optional API key.
Send HTML, MJML, Maizzle or React Email. Set format and the template is compiled before analysis, so what gets checked is the HTML your readers actually receive.
Why your assistant needs this: across the 298 CSS and HTML features we track, only 6 are fully supported in every major email client (see the data). Ask Claude to check your email before you send it.
Built on @emailens/engine. Also available as a GitHub Action.
Install
npx -y @emailens/mcpRelated MCP server: email-validator-api
Setup
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"emailens": {
"command": "npx",
"args": ["-y", "@emailens/mcp"]
}
}
}Claude Code
claude mcp add emailens -- npx -y @emailens/mcpWith API Key (optional, unlocks screenshots + sharing)
{
"mcpServers": {
"emailens": {
"command": "npx",
"args": ["-y", "@emailens/mcp"],
"env": {
"EMAILENS_API_KEY": "ek_live_..."
}
}
}
}Get your free API key at app.emailens.dev/dashboard/api.
Remote (no install)
Use the hosted endpoint: no npm or Node.js needed. API key required.
{
"mcpServers": {
"emailens": {
"url": "https://app.emailens.dev/api/mcp",
"headers": {
"Authorization": "Bearer ek_live_..."
}
}
}
}Tools
Local Tools (no account needed)
preview_email
Full email compatibility preview: transforms HTML for 21 clients, analyzes CSS, generates scores, simulates dark mode, checks inbox preview and email size.
Parameter | Type | Required | Description |
| string | One of | Email HTML source |
| string | One of | Absolute path to the source file instead of |
| string[] | No | Filter to specific client IDs |
| enum | No |
|
analyze_email
Quick CSS compatibility analysis; returns per-client scores and one finding per problem. Faster than audit_email when you only need CSS compatibility.
Parameter | Type | Required | Description |
| string | One of | Email HTML source |
| string | One of | Absolute path to the source file instead of |
| enum | No | Input format |
| enum | No |
|
| string[] | No | Only report these client IDs |
| enum | No |
|
One finding per problem, not one per client. The engine reports per client
because a score is per client, and per selector because a fix is per selector.
On an ordinary newsletter border-radius arrives twelve times (two clients
that drop it, six selectors that use it) with the same sentence in every copy.
That was 286KB of JSON, about 73,000 tokens, for an 11KB email.
Findings group by property, severity and message, listing the clients affected, with positions merged across all of them. The same email now returns 40KB.
{
"property": "border-radius",
"severity": "warning",
"clients": ["outlook-windows", "outlook-windows-legacy"],
"message": "Does not support \"border-radius\". Round corners can be used in VML…",
"fixType": "structural",
"hasFix": true,
"loc": { "line": 61, "column": 28, "offset": 2753, "length": 171 },
"alsoAtLines": [62, 64, 75, 78, 87]
}Fix snippets are not included; they were 93KB of that 286KB, and fix_email
produces them for the issues you decide to act on. hasFix tells you one is
available; fixType tells you whether the repair is markup or CSS.
Pass detail: "full" for the engine's per-client shape with snippets, and
clients: ["gmail-web", "outlook-windows"] to report only what you care about:
the fastest further saving, roughly halving the response for two clients.
Scores stay whole-email either way: narrowing the report does not change what
the email is worth elsewhere. An unknown client ID is rejected by name; an
empty result would read as "this email is fine for that client".
Source positions. For HTML input, every warning carries loc (line,
column, offset, length) for the first occurrence, plus alsoAtLines for
any others, so an assistant can edit the exact source and knows where the rest
are. audit_email positions its other findings the same way.
{
"property": "border-radius",
"loc": { "line": 7, "column": 8, "offset": 142, "length": 25 },
"alsoAtLines": [12, 19]
}Later occurrences are line numbers rather than full positions on purpose: this response is read by a model paying for every token, and a real newsletter can produce over a thousand occurrences; carrying them all in full nearly doubles the payload.
Positions are reported for html input only. JSX, MJML and Maizzle are compiled
before analysis, so a line number would point into generated output rather than
the file you have open: the tools omit it instead of returning one that looks
authoritative.
audit_email
Comprehensive quality audit: CSS compatibility, spam scoring, link validation, accessibility, images, inbox preview, size (Gmail clipping), template variables, content overflow, visual bugs, dark-mode and mobile text contrast, design consistency, and client targeting.
The last three cover what a light desktop preview cannot show: text that disappears when a client forces dark mode or when the email's own dark block repaints a surface without re-colouring the text on it, contrast below the email's breakpoint, and colours that differ by value but not to a reader.
Parameter | Type | Required | Description |
| string | One of | Email HTML source |
| string | One of | Absolute path to the source file instead of |
| enum | No | Input format |
| enum | No |
|
| string[] | No | Only report these client IDs |
| string[] | No | Checks to skip (e.g. |
| enum | No |
|
| enum | No |
|
| string | No | The design to hold this version to, usually your first draft. Omitted: the first version of this email audited in the session. What the edits removed comes back as |
Fix error and warning findings. info findings are not problems: the email falls back safely there, so never remove responsive (@media) or dark-mode CSS to clear them.
fix_email
Generate a structured fix prompt for compatibility issues. Returns markdown with fix instructions that the AI can apply directly.
Parameter | Type | Required | Description |
| string | One of | Email HTML to fix |
| string | One of | Absolute path to the source file instead of |
| enum | No | Controls fix syntax |
| enum | No |
|
| string | No | Client ID for scoped fixes |
list_clients
List all 21 supported email clients with IDs, names, engines, and dark mode support.
diff_emails
Compare two email HTML versions; shows score changes, fixed issues, and introduced issues per client.
Parameter | Type | Required | Description |
| string | One of | Original email source, or its file |
| string | One of | Modified email source, or its file |
| enum | No | Input format |
check_deliverability
Check email deliverability for a domain: SPF, DKIM, DMARC, MX, BIMI records with a score and actionable issues.
Parameter | Type | Required | Description |
| string | Yes | Domain to check (e.g. |
check_design
Whether the email still looks like its design in each client's live preview.
It draws the email in a real browser twice: as the client shows it, and as
you wrote it. Then it compares the two layouts element by element. Each
client gets a verdict, kept (Ready), changed (Needs work) or broken
(Broken), with the reasons: columns that stack, a button that moved or
resized, a fill or corners lost, fonts and spacing changed. This is the
verdict the Emailens email page shows. An agent can call it after an edit to
confirm the fix didn't break the layout somewhere else.
Parameter | Type | Required | Description |
| string | One of | Email HTML source |
| string | One of | Absolute path to the source file instead of |
| string[] | No | Client IDs to check. Default: all 21 (a few seconds each, four at a time) |
| enum | No | Input format |
{ "broken": ["outlook-windows-legacy"],
"results": [{ "clientId": "outlook-windows-legacy", "name": "Outlook Classic",
"verdict": "broken", "label": "Broken",
"sentence": "Outlook Classic breaks your design.",
"reasons": ["Columns that sit side by side in your design stack on top of each other."],
"more": 0 }] }It needs a browser. Add playwright-core to the server, and sharp for the
pixel comparison. Then either install a local Chromium or point it at your
Browserless instance:
{
"mcpServers": {
"emailens": {
"command": "npx",
"args": ["-y", "-p", "@emailens/mcp", "-p", "playwright-core", "-p", "sharp", "emailens-mcp"],
"env": { "BROWSERLESS_URL": "wss://..." }
}
}
}Without BROWSERLESS_URL, it uses a local Chromium. Install one with
npx playwright-core install chromium. A few more things to know:
It runs in light mode, against our live preview, not real inboxes.
With
sharp, it also compares screenshots of the two pages pixel by pixel, as the hosted check does. That agrees more often with a human reviewer, and each result carriesdiff(the share of pixels off) andaligned. Withoutsharp, it compares page structure only.On Browserless, the session has to stay open for the whole call. Raise a short
TIMEOUT, or pass fewerclients.Scripts are off in both pages.
The font stand-ins the previews use are downloaded once from app.emailens.dev into
~/.cache/emailens/fonts.
Hosted Tools (require EMAILENS_API_KEY)
capture_screenshots
Capture real email screenshots across 21 clients in real browsers. Screenshots are hosted on CDN.
Parameter | Type | Required | Description |
| string | One of | Email HTML source |
| string | One of | Absolute path to the source file instead of |
| enum | No | Input format |
| string[] | No | Filter clients |
| string[] | No |
|
| string | No | Name for the preview |
Free plan: 30 previews/day. Sign up
share_preview
Create a shareable link. Recipients see the full analysis without an account.
Parameter | Type | Required | Description |
| string | One of | Email HTML source |
| string | One of | Absolute path to the source file instead of |
| string | No | Display title |
| enum | No | Input format |
Requires Dev plan ($9/mo). Share links expire after 7 days (Dev) or never (Pro).
Template formats
format accepts html (the default), mjml, maizzle and jsx (React
Email). maizzle is an HTML template or a Vue single-file component. A pasted
Vue file with no format is compiled as maizzle. Anything but html is
compiled before analysis and also decides the syntax the fix snippets come back in.
Compiling matters more than it sounds. An email client renders the output, so
that is what has to be checked: handed a raw <mjml> document, an HTML parser
finds no CSS in it and reports a perfectly clean email. An answer like that is
worse than an error, because an assistant will repeat it.
The compilers are not bundled. MJML alone pulls 56MB, and this server is
usually started with npx, so the engine keeps them as optional peer
dependencies:
npm install mjml # MJML
npm install @maizzle/framework@5 # Maizzle HTML
npm install @maizzle/framework@6 # Maizzle Vue single-file components
npm install sucrase react @react-email/components @react-email/render # React EmailThey have to be installed where the server runs, which is not always somewhere
you control. If it is not, compile the template yourself and send the resulting
HTML with format: "html": the tools say so when they hit this.
Supported Email Clients (21)
Each client links to its CSS support page. Setup guides for every assistant: emailens.dev/mcp.
Client | ID | Dark Mode | Notes |
| Yes | ||
| Yes | ||
| Yes | ||
| Yes | ||
| No | ||
| No | Deprecated Oct 2026 | |
| Yes | New in v0.4.0 | |
| Yes | New in v0.4.0 | |
| Yes | New in v0.10.0 | |
| Yes | ||
| Yes | ||
| Yes | ||
| Yes | New in v0.10.0 | |
| Yes | New in v0.10.0 | |
| Yes | ||
| No | ||
| Yes | ||
| Yes | New in v0.10.0 | |
| Yes | New in v0.10.0 | |
| Yes | New in v0.10.0 | |
| Yes |
Releasing
Two publishes: npm, and the MCP registry. The registry listing sat five
releases behind because nothing pushed server.json, so that half is a
workflow now. RELEASING.md has the details and the four
places the version has to agree.
Development
bun install
bun run build
bun test
bun run typecheckLicense
MIT
If this saved you from an Outlook surprise, a star helps other email developers find it.
Available Tools
14 toolsanalyze_emailAnalyze EmailARead-onlyIdempotentInspect
Fix error and warning findings. Info findings are not problems (the email falls back safely there): never remove responsive (@media) or dark-mode CSS to clear them. Quick CSS compatibility analysis, returns per-client scores and one finding per problem, listing the clients it affects. For HTML input each finding carries loc (line, column, offset) and alsoAtLines, so you can edit the exact source. Narrow with clients, or pass detail:'full' for the per-client breakdown with fix snippets. Use audit_email for a full quality report (spam, links, a11y, images, etc.).
Inputs: html, path, detail, format, +2 more.
audit_emailAudit EmailARead-onlyIdempotentInspect
Fix error and warning findings, and restore anything listed in designRemovals. Info findings are not problems (the email falls back safely there): never remove responsive (@media), dark-mode CSS or rounded corners to clear them. designRemovals compares this version with the first one audited for the same email (or with previousHtml): design the edits deleted, such as @media rules, dark mode, corners, gradients, VML fallbacks or images. Comprehensive email quality audit: CSS compatibility, spam scoring, link validation, accessibility, images, inbox preview, size (Gmail clipping), template variables, content overflow, visual fallbacks, dark-mode and mobile text contrast, design consistency, structural faults in Outlook-only VML (which lives inside conditional comments and is invisible to every other check), style survival: CSS a client parses correctly and then discards, such as a stylesheet past Gmail's 16 KB ceiling or every rule after a }}, which no support matrix can express, and client targeting: HowToTarget hacks such as Gmail u+.body or MSO conditionals, which do not score as css-hack. For HTML input, findings tied to a specific element carry loc (line, column, offset) so you can edit the exact source. Compatibility is collapsed to one finding per problem listing the clients it affects; pass detail:'full' for the per-client breakdown with fix snippets. Use skip to omit checks, targetingPolicy to change how targeted scopes affect scores, and clients to narrow which clients are reported.
Inputs: html, path, skip, detail, +5 more.
capture_screenshotsCapture ScreenshotsAInspect
Capture real email screenshots across 21 clients (Gmail, Outlook, Apple Mail, etc.) with light and dark mode variants. Screenshots are rendered in real browsers and hosted on CDN. Requires EMAILENS_API_KEY env var — free plan at emailens.dev?utm_source=mcp.
Inputs: html, path, modes, title, +2 more.
check_deliverabilityCheck DeliverabilityARead-onlyIdempotentInspect
Check email deliverability for a domain: SPF, DKIM, DMARC, MX, and BIMI records. Returns a score (0-100) and actionable issues. Uses DNS lookups (no API key needed).
Inputs: domain (required).
check_designCheck DesignARead-onlyIdempotentInspect
Whether the email still looks like its design in each client's live preview: draws the email as the client shows it and as written, in a real browser, and compares the layouts element by element. Returns per client a verdict (kept = Ready, changed = Needs work, broken = Broken) with the reasons (columns that stack, a button that moved or resized, a fill or corners lost, fonts and spacing changed). Use it after editing an email to confirm a fix did not break the layout. Needs playwright-core installed beside this server and a browser (a local Chromium, or BROWSERLESS_URL); with sharp installed it also compares screenshots pixel by pixel and returns diff and aligned. Light mode, our live preview, not real inboxes.
Inputs: html, path, format, clients.
diff_emailsDiff EmailsARead-onlyIdempotentInspect
Compare two email HTML versions, shows score changes, fixed issues, and newly introduced issues per client. Use after making fixes to verify improvements.
Inputs: after, before, format, afterPath, +1 more.
fix_emailFix EmailARead-onlyIdempotentInspect
Generate a structured fix prompt for email compatibility issues. Returns markdown with the original code, detected issues (CSS or structural), fix snippets, and format-specific instructions. Use after preview_email or analyze_email.
Inputs: html, path, scope, format, +1 more.
list_clientsList Email ClientsARead-onlyIdempotentInspect
List every supported email client with IDs, names, engines, and dark mode support.
Inputs: no named parameters.
preview_emailPreview EmailBRead-onlyIdempotentInspect
Full email compatibility preview, transforms HTML for 21 email clients (Gmail, Outlook, Apple Mail, Yahoo, Samsung, Thunderbird, HEY, Proton Mail, AOL, Fastmail, Superhuman), analyzes CSS, generates scores, simulates dark mode, checks inbox preview and email size.
Inputs: html, path, format, clients, +1 more.
sandbox_get_inboxGet Sandbox InboxAInspect
Get your active Emailens sandbox test address (or create a new one). Send emails here via SMTP (smtp.emailens.dev:2525) or inbound domain routing. Requires EMAILENS_API_KEY.
Inputs: name.
sandbox_get_messageGet Sandbox MessageARead-onlyIdempotentInspect
Get complete captured email details including HTML/text parts, extracted OTP, magic links, headers, and spam analysis. Requires EMAILENS_API_KEY.
Inputs: messageId (required).
sandbox_list_messagesList Sandbox MessagesBRead-onlyIdempotentInspect
List recently received test emails in your sandbox inboxes. Requires EMAILENS_API_KEY.
Inputs: inboxId.
sandbox_wait_for_emailWait for Sandbox EmailARead-onlyInspect
Poll and wait for a matching incoming test email in the sandbox. Automatically extracts 4-8 digit OTP codes and action links for zero-regex test assertions. Requires EMAILENS_API_KEY.
Inputs: sender, inboxId, subject, timeoutSeconds.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools have distinct roles, and the intended sequence from preview/analyze/audit to fix/diff is clear. However, preview_email, analyze_email, and audit_email all report compatibility or quality findings, so an agent may need to read descriptions carefully to select the right one.
Names are consistently snake_case and mostly follow an action/resource pattern such as list_clients, check_design, and preview_email. Minor deviations appear with the sandbox_* prefix and email/emails pluralization, but the overall naming remains predictable.
With 14 tools, the server sits comfortably in the well-scoped 3-15 range. Each tool maps to a meaningful capability, including analysis, design checking, screenshots, deliverability, sharing, and sandbox testing.
The set covers the main email QA lifecycle: client listing, previewing, compatibility analysis, auditing, fixing, diffing, deliverability, screenshots, sharing, and sandbox message inspection. Minor gaps exist around direct sandbox sending/cleanup, but those are largely handled through SMTP or external workflows.
Maintenance
Related MCP Connectors
Screenshots, PDFs, image editing, QR codes, email validation and more through one hosted MCP server.
MCP server for e-mail testing: create disposable inboxes, wait for delivery, and extract e-mail content or links - all from your AI agent or test automation workflow. Get a free API key on https://app.zyntra.app/
Send transactional email and manage domains, audiences, and broadcasts from any MCP client.
Hosted MCP server for custom-domain email: send, receive and wait for mail on your domain.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceAn MCP server exposing every documented Email on Acid API v5 request as a tool — 24 tools across authentication, email client lists, email rendering testing, and spam testing.MIT- AlicenseNot gradedqualityDmaintenanceComprehensive email validation MCP server that checks syntax, MX records, disposable domains, role-based accounts, SPF/DKIM, typo suggestions, and risk scoring.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing email client compatibility data from caniemail.com, enabling agents to lint HTML/CSS for email client support, check feature support across clients, and search for features by keyword, with verdicts including supported, unsupported, mitigated, and untested.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes an email verification tool, returning verdicts of valid, invalid, or risky with reasons.-