# HTML Email Playbook
> Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 19 rules, 6 comps.
- name: io.github.OsamaHassouna/email-playbook-mcp
- version: 0.7.0
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 74/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.OsamaHassouna%2Femail-playbook-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.OsamaHassouna%2Femail-playbook-mcp/tools
**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.
## Connection (mcpServers)
```json
{
"mcpServers": {
"email-playbook-mcp": {
"type": "http",
"url": "https://docs.osamahassouna.com/api/mcp"
}
}
}
```
## Trust
- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-3d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.
## Quality 74/100 (needs work)
### protocol: 75 (weight 25)
- warn `protocol.modern`: newest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers
### authorization: n/a (weight 15)
- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL
### tool hygiene: 86 (weight 30)
- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_categories (destructiveHint); get_playbook_rules (destructiveHint); get_rule (destructiveHint); …
- pass `tools.token_cost`: about 881 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
### stability: 50 (weight 15)
- pass `stability.changes`: 5 tool changes in 30 days
- fail `stability.rug_pull`: 1 tools kept their name but changed most of their description in 30 days; review before trusting them
### dependencies: n/a (weight 15)
- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: deps.dev does not know email-playbook-mcp@0.7.0
- tools: 5, about 881 tokens to load them all
- tool set hash: 3707f0c8ddbc8cc363b314605d09b59f
- tools last changed: 2026-10-17T16:39:04.449Z
- badge: [](https://protogrid.dev/servers/io.github.OsamaHassouna/email-playbook-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.
### Tool changes
- 2026-10-17 `get_component` changed (annotations)
- 2026-10-17 `list_components` changed (annotations)
- 2026-10-17 `get_rule` added
- Return 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/"). Get the slugs from list_categories. Much smaller than fetching the whole category with get_playbook_rules.
- 2026-10-17 `get_playbook_rules` changed (description, inputSchema, annotations) **meaning changed**
- before: 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).
- after: Return 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, markdown body and all HTML/CSS code examples. Start with the checklists, then fetch the pages you need with get_rule. Components are not included: use list_components / get_component.
- 2026-10-17 `list_categories` changed (description, annotations)
- before: 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.
- after: List 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, bulletproof buttons), ai-generation (constraints for AI emitters). Pass a page slug to get_rule to fetch just that page. For reusable components, use list_components instead — they live in a separate dimension and are not returned by get_playbook_rules.
Full history: https://api.protogrid.dev/v1/servers/io.github.OsamaHassouna%2Femail-playbook-mcp/changes
## Dependencies
- npm email-playbook-mcp@0.7.0: unknown
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0.
## Remotes
- https://docs.osamahassouna.com/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)
## Packages
- npm email-playbook-mcp@0.7.0
## Tools (5)
- `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.
- `get_playbook_rules`: Return 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, markdown body and all HTML/CSS code examples. Start with the checklists, then fetch the pages you need with get_rule. Components are not included: use list_components / get_component.
- `get_rule`: Return 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/"). Get the slugs from list_categories. Much smaller than fetching the whole category with get_playbook_rules.
- `list_categories`: List 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, bulletproof buttons), ai-generation (constraints for AI emitters). Pass a page slug to get_rule to fetch just that page. 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.