HTML Email Playbook
Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.
使うべきか
品質と安全性
検出事項（3）
- HIGHTool poisoning patterns detected
- MEDIUMTool 'get_component' description contains placeholder textget_component 内
- INFOTool description contains placeholder or incomplete textget_component 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"email-playbook-mcp": {
"command": "npx",
"args": [
"email-playbook-mcp"
]
}
}
}実行可能なパッケージ
0.6.3stdioリモートエンドポイント
https://docs.osamahassouna.com/api/mcpstreamable-httpできること
ツール一覧
ツール（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.
入力スキーマ
{
"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).
入力スキーマ
{
"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.
入力スキーマ
{
"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.
入力スキーマ
{
"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
}コミュニティ
エビデンス