M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
E

EmailMD MCP Server

Community
Render markdown into email-safe HTML
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #176 of 438
Stars
★ 1.4k Very popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js 20+ · Hosted (no local runtime)
Credentials
No credential needed
License
MIT
Last commit
Tools
3
56FMRS · C

emailmd provides core functionality for rendering markdown to email-safe HTML, with lint and documentation tools. It suits developers generating email templates quickly, but note it is not officially maintained by a protocol owner, and outputs should be human-reviewed.

Strongest · Setup experience 13/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
11/20
Maintenance
13/20
Documentation
13/20
Setup experience
13/20
Why each score
Reliability 6/20
The manifest and README describe a two-transport MCP server (stdio via the npm package emailmd, plus a hosted streamable-http endpoint). The README lists three tools (render, lint, read_docs), but the manifest description claims 'preview emails,' and the README's own MCP paragraph says 'render, lint, and preview' before naming read_docs as the third tool — an internal contradiction. No source files, tests, or CI workflows were supplied, so clean startup, the init/tool-list handshake, and real tool behavior cannot be verified. The happy path is plausible for a published npm package, but there is no execution evidence; points deducted for the tool-list contradiction and missing verification.
Security and permissions 11/20
No red-line risks are evident: no credential handling, no destructive defaults, and no install examples containing real tokens. The main data-boundary consideration is visible: the hosted streamable-http endpoint (https://www.emailmd.dev/api/mcp) would send email drafts to a third-party service, while a local stdio mode is offered as the more private alternative. Source code was not available to audit actual data flow, and the hosted endpoint has no stated retention/logging policy; permission/confirmation and scoping details are incomplete. No malware, exfiltration, or fabricated artifacts were found, so no red line is triggered, but full marks are not justified.
Maintenance 13/20
The project has an MIT license, the repository is not archived, open issues are zero, version is 0.10.0, and there is an explicit stability/versioning section referencing a semver contract and changelog, with a named sponsor (Anypost) indicating clear ownership. Changelog and breaking-change notes are referenced. However, the supplied evidence includes no commit/release dates, no issue-response records, and no security-response channel, so sustained maintenance is plausible but not fully evidenced. Points deducted for missing release-history and vulnerability-reporting evidence.
Documentation 13/20
Layered documentation is evident: README quick start, async render() migration note, CLI flags, React hooks, MCP transports, a full docs site, and an llms-full.txt for AI context. Limitations are disclosed (pre-1.0 API changes, breaking changes called out in changelog). Gaps: no per-tool parameter schemas for the MCP tools, no rate-limit/cost information for the hosted endpoint, no troubleshooting section, and the 'preview emails vs read_docs' inconsistency. Points deducted for these missing specifics.
Setup experience 13/20
Setup paths are short and concrete: run locally with `npx emailmd mcp` (npm package [email protected], stdio) or point the client at the hosted streamable-http URL; registration in the official MCP registry (dev.emailmd/emailmd) simplifies discovery. Node 20+ is stated as a requirement. However, no per-client configuration examples appear in the supplied material (only a link to the MCP docs), and there is no committed CI/tests evidence to raise setup above 15 under the static-calibration cap. Points deducted for absent client-config examples and verification evidence.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Developers who need quick markdown-to-HTML conversion
  • Teams that want to lint email drafts for deliverability
  • AI workflows that generate email content

Not for

  • Users needing a full email marketing platform
  • Use cases requiring tracking and analytics
  • Users wanting a drag-and-drop editor

Required permissions

  • Network access for remote endpoint (streamable-http)
  • Node.js 20+ environment for local stdio

Risks and side effects

  • Output may require manual review for edge cases
  • Depends on MJML under the hood, adding indirect dependency risk

Setup

Before you start

Runtime：Node.js 20+ · Hosted (no local runtime)

Run npx emailmd mcp locally (stdio) or use the hosted HTTP endpoint https://www.emailmd.dev/api/mcp (streamable-http). For Claude Desktop, configure with the appropriate transport.

Check that it works

After connecting the client to https://www.emailmd.dev/api/mcp (or running npx emailmd mcp over stdio), the tools render, lint, and read_docs should appear in the client's tool list; asking the AI to render "# Hello" via render confirms the connection works.

Troubleshooting

  1. Ensure Node.js >= 20 (render is async since v0.3.0)
  2. Check network connectivity if using the hosted endpoint
  3. Refer to https://www.emailmd.dev/docs/mcp for client setup

Things to try

Once connected, you can ask your AI assistant things like:

  • Render this markdown into email-safe HTML: # Welcome! Thanks for signing up.
  • Lint this email draft for deliverability problems.
  • Use read_docs to look up the emailmd button directive syntax.
  • Convert this markdown to email HTML and also give me the plain-text version.

Tools 3

render read-only
Render markdown to email-safe HTML
lint read-only
Flag deliverability problems without rendering
read_docs read-only
Look up emailmd syntax

Use cases

Generate email templates from markdown
Check email deliverability issues
Preview emails in a live editor

Overview

emailmd is an MCP server that converts Markdown into responsive, email-safe HTML that works across Gmail, Outlook, Apple Mail, Yahoo, and more. It exposes three tools: render (markdown to email-safe HTML), lint (flag deliverability problems), and read_docs (look up emailmd syntax). Supports both Streamable HTTP and stdio transports.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 391ffc1b0d36 Data synced 2026-10-12 Read the FMRS scoring method