All servers · Email & messaging
HTML Email Playbook
io.github.OsamaHassouna/email-playbook-mcp · v0.7.0
New (7 days)Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2024-11-05 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.
Connect
streamable-http · https://docs.osamahassouna.com/api/mcp
claude mcp add --transport http email-playbook-mcp https://docs.osamahassouna.com/api/mcp{
"mcpServers": {
"email-playbook-mcp": {
"url": "https://docs.osamahassouna.com/api/mcp"
}
}
}Tools as reported by the server
list_categoriesList all rule categories in the Email Playbook with a one-line description, page count, and the slug and title of each page in it. Categories are: structure (head/body container/header/body/footer), compatibility (Outlook MSO, RTL, responsive), production (Gmail clipping, dark mode, preheader, bulleget_playbook_rulesReturn rule pages. format "checklist": each page as its slug, title, description and a short list of the rules to follow, without the body or code; leave out category to get every page in one call (about 16 KB). format "full" (default, needs a category): each page with title, description, checklist,get_ruleReturn one rule page: slug, category, title, description, checklist, and the markdown body, which includes the page's HTML/CSS code. Accepts the full slug (e.g. "compatibility/responsive"), just the page name ("responsive"), or a page link from a body ("/email-playbook/compatibility/responsive/"). Glist_componentsList 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.get_componentReturn 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.
Tool changes
- 2026-10-18: list_categories, get_playbook_rules, get_rule, list_components, get_component
- 2026-10-16: list_categories, get_playbook_rules, list_components, get_component
Repository · Website · JSON · Text for agents · Registry updated 2026-10-17