MCP-Server

HTML Email Playbook

io.github.OsamaHassouna/email-playbook-mcp
Marketing & Werbung Öffentlich und erreichbar MCP 2026-07-28

Was dieses MCP kann

Provides rules, reusable components, and HTML patterns for creating email templates compatible with major mail clients.

get_component
Return the full record for a single component: title, description, narrative body, the primary HTML pattern, list of slots (placeholders the model should fill), VML/responsive flags, and all code examples. Use after list_components to fetch the actual HTML pattern to paste into an email.
Eingabeschema
{'type': 'object', 'required': ['name'], 'properties': {'name': {'enum': ['background-images', 'buttons', 'images', 'inline-icon', 'spacing', 'text'], 'type': 'string', 'description': 'Component name. Get the list from list_components first.'}}, 'additionalProperties': False}
get_playbook_rules
Return the full rule pages for a given category. Each rule includes the title, description, markdown body explaining the rule, and any HTML/CSS code examples from the playbook. Use this to teach a model the exact patterns for a specific concern (e.g., responsive layout).
Eingabeschema
{'type': 'object', 'required': ['category'], 'properties': {'category': {'enum': ['ai-generation', 'compatibility', 'production', 'structure'], 'type': 'string', 'description': 'Which rule category to fetch.'}}, 'additionalProperties': False}
list_categories
List all rule categories in the Email Playbook with a one-line description and page count. Categories are: structure (head/body container/header/body/footer), compatibility (Outlook MSO, RTL, responsive), production (Gmail clipping, dark mode, preheader, bulletproof buttons), ai-generation (constraints for AI emitters). For reusable components, use list_components instead — they live in a separate dimension and are not returned by get_playbook_rules.
Eingabeschema
{'type': 'object', 'properties': {}, 'additionalProperties': False}
list_components
List all reusable email components in the playbook with their metadata: name, subcategory (layout/media/interactive/text), description, whether they require Outlook VML, and whether they are responsive. Use this first to discover what components exist before calling get_component.
Eingabeschema
{'type': 'object', 'properties': {}, 'additionalProperties': False}
Hinzugefügt
get_component
17. September 2026 12:45
Hinzugefügt
list_components
17. September 2026 12:45
Hinzugefügt
get_playbook_rules
17. September 2026 12:45
Hinzugefügt
list_categories
17. September 2026 12:45