Analyze, audit, and fix HTML, MJML, Maizzle, and React Email templates across 21 email clients to ensure compatibility and deliverability.
Also known as emailens/mcp, mcp, @emailens/mcp
- Stars
- 8
- Tools
- 15
- Downloads, 30 days
- 2,314
- Latest version
- 0.16.0
- Last commit
- Nov 12, 2026
- License
- MIT
What is Emailens MCP?
Emailens is an MCP server. Analyze, audit, and fix HTML, MJML, Maizzle, and React Email templates across 21 email clients to ensure compatibility and deliverability. It exposes 15 tools, such as preview_email, analyze_email, audit_email.
Summary generated from the project's README
About Emailens MCP server
Ensuring email templates render correctly across different inbox providers is what Emailens MCP enables for developers and designers. By integrating this server with Claude Desktop or Claude Code, you can analyze, audit, and fix email code to prevent broken layouts and deliverability issues. The tool supports various input formats including HTML, MJML, Maizzle, and React Email, compiling them before analysis to ensure the results reflect the actual code sent to readers.
Users can perform quick CSS compatibility checks with analyze_email or run a comprehensive audit_email to check for spam scores, accessibility, and dark mode issues. For those needing visual verification, the server offers hosted tools like capture_screenshots and share_preview, which require an optional API key. It tracks 298 CSS and HTML features across 21 different email clients, providing specific line numbers and fix instructions to help an AI assistant repair your templates directly.
What you can do with it
- 1Audit email compatibilityCheck if your email template will render correctly across 21 different email clients.
Written from the project's README. Every use case is checked against a quote from it.
How to install Emailens MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Emailens MCP in Claude Code
$ claude mcp add --env 'EMAILENS_API_KEY=<YOUR_EMAILENS_API_KEY>' mcp -- npx -y @emailens/mcpInstall Emailens MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@emailens/mcp"
],
"env": {
"EMAILENS_API_KEY": "<YOUR_EMAILENS_API_KEY>"
}
}
}
}Install Emailens MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@emailens/mcp"
],
"env": {
"EMAILENS_API_KEY": "<YOUR_EMAILENS_API_KEY>"
}
}
}
}Install Emailens MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@emailens/mcp"],"env":{"EMAILENS_API_KEY":"<YOUR_EMAILENS_API_KEY>"}}'Install Emailens MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@emailens/mcp"
],
"env": {
"EMAILENS_API_KEY": "<YOUR_EMAILENS_API_KEY>"
}
}
}
}Install Emailens MCP in Codex
$ codex mcp add mcp --env 'EMAILENS_API_KEY=<YOUR_EMAILENS_API_KEY>' -- npx -y @emailens/mcpInstall Emailens MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@emailens/mcp"] [mcp_servers.mcp.env] EMAILENS_API_KEY = "<YOUR_EMAILENS_API_KEY>"
Install Emailens MCP in Gemini CLI
$ gemini mcp add -s user -e 'EMAILENS_API_KEY=<YOUR_EMAILENS_API_KEY>' mcp npx -- -y @emailens/mcpInstall Emailens MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@emailens/mcp"
],
"env": {
"EMAILENS_API_KEY": "<YOUR_EMAILENS_API_KEY>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @emailens/mcp 0.16.0 in an isolated container with no network and no keys. It answered and listed 14 tools.
Emailens MCP tools 15
Read from the server with tools/listpreview_emailRead-onlyFull email compatibility preview , transforms HTML for 21 email clients, analyzes CSS, generates scores, previews dark mode, checks inbox preview and email size.
analyze_emailRead-onlyFix 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.).
audit_emailRead-onlyFix 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, style survival (CSS a client parses and then discards, such as a stylesheet past Gmail's 16 KB ceiling or every rule after a `}}`), and client targeting (HowToTarget hacks such as Gmail u+.body or MSO conditionals). For HTML input, findings tied to a specific element carry loc (line, column, offset). 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.
fix_emailRead-onlyGenerate a structured fix prompt for email compatibility issues.
list_clientsRead-onlyList all 21 supported email clients with IDs, names, rendering engines, dark mode support, and deprecation status. Use the returned IDs to filter other tools like preview_email or capture_screenshots.
diff_emailsRead-onlyCompare two email HTML versions , shows score changes, fixed issues, and regressions per client.
capture_screenshotsActionCapture 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.
share_previewActionCreate a shareable link for an email preview. Recipients see the full analysis without needing an account. Requires the Dev plan or above.
check_deliverabilityRead-onlyCheck email deliverability for a domain , SPF, DKIM, DMARC, MX, BIMI.
build_emailActionGenerate a cross-client-compatible email from a brief using Emailens's self-healing loop (generate → score across 21 clients → repair). Output stays in the framework you choose. Returns a runId immediately , poll get_build_status for progress and the final code. Requires a Pro/Team API key.
get_build_statusRead-onlyCheck a build_email run by runId , returns status, iteration, best compatibility score, and the current best source once available.
sandbox_get_inboxActionRetrieve or auto-create your Emailens sandbox test email address for capturing test emails.
Show all 15 toolsShow fewer tools
sandbox_list_messagesRead-onlyList recently captured test emails in the Emailens sandbox.
sandbox_wait_for_emailRead-onlyPoll and wait for a matching incoming test email in the sandbox (ideal for auth OTPs, magic links, transactional email assertions).
sandbox_get_messageRead-onlyGet complete email details: HTML/text body, parsed headers, spam score, SPF/DKIM/DMARC auth status, and validated links.
Configuration
EMAILENS_API_KEYSecretAPI key for screenshots and sharing. Get one free at app.emailens.dev/dashboard/api
BROWSERLESS_URL
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableemailens/mcp is public and reachablegithub.com/emailens/mcp ↗Pass
- Package names this repository as its source@emailens/mcp names emailens/mcp as sourcenpmjs.com/package/@emailens/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/emailens/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @emailens/mcpPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model15 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-11-25 in 635 ms; tools/list returned 15 toolsPass
README
View on GitHubEmail 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/mcp
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/mcp
With 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 |
|---|---|---|---|
html |
string | One of | Email HTML source |
path |
string | One of | Absolute path to the source file instead of html (.html, .htm, .mjml, .jsx, .tsx, .vue); the extension sets format |
clients |
string[] | No | Filter to specific client IDs |
format |
enum | No | "html", "jsx", "mjml", "maizzle" |
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 |
|---|---|---|---|
html |
string | One of | Email HTML source |
path |
string | One of | Absolute path to the source file instead of html (.html, .htm, .mjml, .jsx, .tsx, .vue); the extension sets format |
format |
enum | No | Input format |
detail |
enum | No | "summary" (default) or "full" |
clients |
string[] | No | Only report these client IDs |
targetingPolicy |
enum | No | "progressive" (default), "strict", or "lenient" |
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 |
|---|---|---|---|
html |
string | One of | Email HTML source |
path |
string | One of | Absolute path to the source file instead of html (.html, .htm, .mjml, .jsx, .tsx, .vue); the extension sets format |
format |
enum | No | Input format |
detail |
enum | No | "summary" (default) or "full" |
clients |
string[] | No | Only report these client IDs |
skip |
string[] | No | Checks to skip (e.g. ["spam", "images"]) |
targetingPolicy |
enum | No | "progressive" (default), "strict", or "lenient" |
emailType |
enum | No | "transactional" (no unsubscribe link required) or "marketing". Omitted: guessed from the content |
previousHtml |
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 designRemovals |
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 |
|---|---|---|---|
html |
string | One of | Email HTML to fix |
path |
string | One of | Absolute path to the source file instead of html (.html, .htm, .mjml, .jsx, .tsx, .vue); the extension sets format |
format |
enum | No | Controls fix syntax |
scope |
enum | No | "all" or "current" |
selectedClientId |
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 |
|---|---|---|---|
before / beforePath |
string | One of | Original email source, or its file |
after / afterPath |
string | One of | Modified email source, or its file |
format |
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 |
|---|---|---|---|
domain |
string | Yes | Domain to check (e.g. "company.com") |
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 |
|---|---|---|---|
html |
string | One of | Email HTML source |
path |
string | One of | Absolute path to the source file instead of html |
clients |
string[] | No | Client IDs to check. Default: all 21 (a few seconds each, four at a time) |
format |
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 |
|---|---|---|---|
html |
string | One of | Email HTML source |
path |
string | One of | Absolute path to the source file instead of html (.html, .htm, .mjml, .jsx, .tsx, .vue); the extension sets format |
format |
enum | No | Input format |
clients |
string[] | No | Filter clients |
modes |
string[] | No | ["light"], ["dark"], or ["light", "dark"] |
title |
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 |
|---|---|---|---|
html |
string | One of | Email HTML source |
path |
string | One of | Absolute path to the source file instead of html (.html, .htm, .mjml, .jsx, .tsx, .vue); the extension sets format |
title |
string | No | Display title |
format |
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 Email
They 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 |
|---|---|---|---|
| Gmail | gmail-web |
Yes | |
| Gmail Android | gmail-android |
Yes | |
| Gmail iOS | gmail-ios |
Yes | |
| Outlook 365 | outlook-web |
Yes | |
| Outlook Windows | outlook-windows |
No | |
| Outlook Windows Legacy | outlook-windows-legacy |
No | Deprecated Oct 2026 |
| Outlook iOS | outlook-ios |
Yes | New in v0.4.0 |
| Outlook Android | outlook-android |
Yes | New in v0.4.0 |
| Outlook for Mac | outlook-macos |
Yes | New in v0.10.0 |
| Apple Mail | apple-mail-macos |
Yes | |
| Apple Mail iOS | apple-mail-ios |
Yes | |
| Yahoo Mail | yahoo-mail |
Yes | |
| Yahoo Mail Android | yahoo-mail-android |
Yes | New in v0.10.0 |
| Yahoo Mail iOS | yahoo-mail-ios |
Yes | New in v0.10.0 |
| Samsung Mail | samsung-mail |
Yes | |
| Thunderbird | thunderbird |
No | |
| HEY Mail | hey-mail |
Yes | |
| Proton Mail | protonmail |
Yes | New in v0.10.0 |
| AOL Mail | aol |
Yes | New in v0.10.0 |
| Fastmail | fastmail |
Yes | New in v0.10.0 |
| Superhuman | superhuman |
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 typecheck
License
MIT
If this saved you from an Outlook surprise, a star helps other email developers find it.
Emailens MCP questions
How do I add Emailens MCP to Claude Code?
Run claude mcp add --env 'EMAILENS_API_KEY=<YOUR_EMAILENS_API_KEY>' mcp -- npx -y @emailens/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Emailens MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Emailens MCP provide?
It exposes 15 tools, including preview_email, analyze_email, audit_email, fix_email, list_clients.
How many email clients are analyzed?
The server provides analysis and previews for 21 different email clients.