Email Playbook MCP
An MCP server and CLI that teaches AI clients like Claude Desktop and Cursor to write HTML email templates that render reliably across Outlook, Gmail, and Apple Mail by providing structured tools for rules and component patterns.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://docs.osamahassouna.com/api/mcpWhat its tools do
5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Generate HTML email templates compliant with cross-client rendering rules
- Fetch specific component patterns like bulletproof buttons or spacing
- Convert design screenshots into production-ready HTML via the playground
- Validate email structure against absolute rules for AI emitters
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- email-playbook 0.8.0
- MCP protocol negotiated in check
- 2024-11-05
- Tools
- 5 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
5 advertised
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.
{
"type": "object",
"properties": {},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}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.
{
"type": "object",
"properties": {
"format": {
"enum": [
"full",
"checklist"
],
"type": "string",
"description": "full (default): whole pages with code. checklist: titles and rules only."
},
"category": {
"enum": [
"ai-generation",
"compatibility",
"production",
"structure"
],
"type": "string",
"description": "Which rule category to fetch. Required for format \"full\"; optional for \"checklist\"."
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}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.
{
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Page slug, e.g. \"compatibility/responsive\" or \"responsive\"."
},
"include_examples": {
"type": "boolean",
"description": "Also return the code examples as a separate array (they are already in the body). Default false."
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}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
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}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.
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"enum": [
"background-images",
"buttons",
"images",
"inline-icon",
"spacing",
"text"
],
"type": "string",
"description": "Component name. Get the list from list_components first."
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-06: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 405 ms
- 95th percentile latency
- 405 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 405 ms · metadata changed · 5 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http email-playbook-mcp https://docs.osamahassouna.com/api/mcpCodex
codex mcp add email-playbook-mcp --url https://docs.osamahassouna.com/api/mcpCursor
{
"mcpServers": {
"email-playbook-mcp": {
"url": "https://docs.osamahassouna.com/api/mcp"
}
}
}Cline
{
"mcpServers": {
"email-playbook-mcp": {
"type": "streamableHttp",
"url": "https://docs.osamahassouna.com/api/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"email-playbook-mcp": {
"type": "http",
"url": "https://docs.osamahassouna.com/api/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http email-playbook-mcp https://docs.osamahassouna.com/api/mcpClaude Desktop
https://docs.osamahassouna.com/api/mcpWindsurf
{
"mcpServers": {
"email-playbook-mcp": {
"serverUrl": "https://docs.osamahassouna.com/api/mcp"
}
}
}Let your agent find its tools
Find servers like Email Playbook MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.