mcp server
HTML Email Playbook
Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.
Description as published by the maintainer. Source
- version 0.6.3
- active
active — Registry entry last updated 2026-06-02.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
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. Required: name.
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). Required: category.
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.
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.
Last successful function declaration observed on . Source: https://docs.osamahassouna.com/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://docs.osamahassouna.com/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.6.3 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | docs.osamahassouna.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | docs.osamahassouna.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json