HTML Email Playbook MCP Server

by osamahassouna Your server? Claim it

not responding

HTML Email Playbook is listed as active in the registry but did not answer our last check. 114 installs a week from npm. It exposes 5 tools. Last commit 31 Oct 2026.

Teaches AI to write HTML email that renders in Outlook, Gmail, and Apple Mail. 21 rules, 6 comps.

Installs per day peak 31 · avg 8 · -29% w/w

a month agotoday

Uptime history 91 days of history · worst day 0%

91 days agonow

14.1%

Uptime 24h

13 of 92 checks

Tools

read from the server

336 ms

Response time

average over 24h

114

Installs / week

npm and PyPI

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

18 Oct 2 tool descriptions were rewritten get_playbook_rules, list_categories

18 Oct a tool appeared get_rule

18 Oct a tool changed the parameters it asks for get_playbook_rules

HTML Email Playbook does not always answer

Over the last week it answered 20.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add email-playbook-mcp --transport http https://docs.osamahassouna.com/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://docs.osamahassouna.com/api/mcp

~/.codex/config.toml

[mcp_servers.email-playbook-mcp]
url = "https://docs.osamahassouna.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "email-playbook-mcp": {
      "url": "https://docs.osamahassouna.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "email-playbook-mcp": {
      "type": "http",
      "url": "https://docs.osamahassouna.com/api/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

categories

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.

component

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.

components

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.

playbook

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.

rule

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.

Endpoints

URL	Transport	State	Latency	Checked
https://docs.osamahassouna.com/api/mcp	streamable-http	answering	63 ms	2 min ago

Alternatives to HTML Email Playbook

same job, measured the same way

Inbox Preview

by powerline

Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them

4 tools answering

Email2Chat

by bayramcsb

Connect Claude to your Gmail and Outlook inbox. Read, search, and manage emails via AI.

148 installs/wk local only

SignatureForever

by signatureforever

Audit and build email signatures that survive Gmail, Outlook desktop and Apple Mail.

5 tools answering

Calensync

by calensync

Manage Google, Outlook & Apple calendars and create private sync rules from chat.

answering

Easy Email Builder

by shahkarkhan440

Design HTML email templates with AI: render to HTML and open them in a visual editor

103 installs/wk local only

Inbox Triage

by getinboxtriage

Connect Gmail, Outlook, iCloud, Yahoo and IMAP to AI apps in one MCP connection.

answering

Inbox Zero

by elie222

Search Gmail and Outlook, save drafts, manage email rules, and view email stats.

answering

Domain Mail Check

by openkrill

Check a domain's email DNS, whether Gmail and Outlook accept its mail, and its registration.

8 tools answering

HTML Email Playbook — questions

Answers built from our own checks of this server.

What can HTML Email Playbook do?

It exposes 5 tools, read directly from the server on our last check. Among them: get_component, get_playbook_rules, get_rule, list_categories, list_components. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is HTML Email Playbook working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 13 of 92 checks got a reply (14.1%), average response time 336 ms. The bar chart above shows every period we have measured.

The registry lists HTML Email Playbook as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect HTML Email Playbook?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does HTML Email Playbook need an API key?

No. HTML Email Playbook completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is HTML Email Playbook?

It answers our handshake in 336 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use HTML Email Playbook?

The npm package email-playbook-mcp was installed 114 times in the last week. Week over week that is -29%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is HTML Email Playbook open source?

The code is open source: it is published under the MIT licence, written in MDX and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at docs.osamahassouna.com, which runs on its operator's own terms.