HTML Email Playbook
Related Servers
Alternatives to HTML Email Playbook
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to check email HTML for delivery-breaking problems before sending, returning structured diagnostics with rule id, severity, line and column, along with a tool that lists every available rule. It runs with no filesystem, network or environment access, so agents can validate markup without gaining new permissions.26 npm3MIT
- AlicenseAqualityAmaintenanceLocal-first visual design workspace for AI assistants. Compose wireframes and branded multi-page HTML/CSS documents with live preview, annotations, brand and asset libraries, typed data collections, layout validation, PDF export, and draft-only Gmail handoff.165 npm20MIT
- FlicenseNot gradedqualityDmaintenanceProvides SMTP integration for sending HTML emails and specialized prompts for intent detection and client information extraction. It enables LLMs to automate personalized email workflows and structure user communication data.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible agents to analyze a brand website, build a custom email design system, assemble responsive HTML campaigns, QA rendering, and export production-ready email.MIT
- AlicenseNot gradedqualityBmaintenanceEnables small models to turn a short brief into complete HTML pages or looping GIFs with typography, palette, borders, motion, and validation already decided. It also lets agents list styles, retrieve style rules, create assets, validate HTML, and access reference examples.MIT

Temway MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceLet your AI assistant design beautiful emails & layouts — in your Temway workspace. It turns Claude, ChatGPT, Cursor and friends into a visual email & layout authoring studio.1MIT
TDQS
Scored across 5 tools
get_playbook_rules and get_rule both return rule pages, which could cause confusion, but the descriptions clearly differentiate (bulk/checklist vs single full page). list_categories and get_playbook_rules also overlap in returning rule metadata, but the separation of rules vs components is well-articulated.
Consistent list_/get_ verb prefixes throughout (list_categories, list_components, get_rule, get_component, get_playbook_rules). Minor noun inconsistency between 'rule' and 'playbook_rules' is the only deviation, still readable and predictable.
Five tools is well-scoped for a read-only reference/playbook server, with a clean 2x2 structure of listing and fetching rules and components, plus category listing. Each tool earns its place.
The surface covers discovery and retrieval for both rule pages and components, which is the core lifecycle for a documentation server. A search tool or a way to fetch multiple specific rules by slug could improve it, but core workflows are fully served.