HTML Email Playbook
Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.
¿Debería usar esto?
Calidad y seguridad
Hallazgos (3)
- HIGHTool poisoning patterns detected
- MEDIUMTool 'get_component' description contains placeholder texten get_component
- INFOTool description contains placeholder or incomplete texten get_component
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"email-playbook-mcp": {
"command": "npx",
"args": [
"email-playbook-mcp"
]
}
}
}Paquetes ejecutables
0.6.3stdioPuntos de conexión remotos
https://docs.osamahassouna.com/api/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (4)
🟢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.
Esquema de entrada
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢get_playbook_rules(category)
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).
Esquema de entrada
{
"type": "object",
"properties": {
"category": {
"type": "string",
"enum": [
"ai-generation",
"compatibility",
"production",
"structure"
],
"description": "Which rule category to fetch."
}
},
"required": [
"category"
],
"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.
Esquema de entrada
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟢get_component(name)
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.
Esquema de entrada
{
"type": "object",
"properties": {
"name": {
"type": "string",
"enum": [
"background-images",
"buttons",
"images",
"inline-icon",
"spacing",
"text"
],
"description": "Component name. Get the list from list_components first."
}
},
"required": [
"name"
],
"additionalProperties": false
}Comunidad
Evidencia