email-template vs emailmd
email-template is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
email-template is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. emailmd is an MCP server published by emailmd.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  emailmd | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.13.2 Downloads/month (npm): 25 900 Downloads/week (npm): 2 655 Forks (GitHub): 39 Stars (GitHub): 1 383 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | email-templateno longer listed · | emailmd |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 1 383 |
| Forks (GitHub) (differs) | 0 | 39 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (www.emailmd.dev/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/anypost/emailmd |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of email-template
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Design and build responsive HTML email templates using Foundation for Emails, Maizzle, or MJML. Framework-agnostic authoring with email-client compatibility baked in.
-
Design HTML email templates with AI: render to HTML and open them in a visual editor
-
Build responsive HTML email campaigns from any brand website: design, QA, export.
-
Unlayer: Email, Page & Document Templates for Developers
Generate email, page & PDF document templates as React code (Unlayer Elements) or AI; edit visually.
-
Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.
-
APITemplate.io MCP by usefulapi
Generate PDFs and images with APITemplate.io from templates, HTML, Markdown or a URL.
What each says it does
email-template
Generate responsive HTML email templates
emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
How to run each
email-template
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
emailmd As a remote MCP server
claude mcp add --transport http emailmd https://www.emailmd.dev/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only emailmd has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: email-template · What it can do: emailmd · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.