Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

Create Rich Email Draft

create_rich_email_draft

Generate rich-text or HTML email drafts as unsent .eml files, then optionally open them in Apple Mail so formatted content renders correctly.

Instructions

Create a rich-text email draft by generating an unsent .eml message and optionally opening it in Mail.

This is the preferred path for HTML or richly formatted emails because Mail reliably renders .eml content, while setting raw HTML through AppleScript often stores the literal markup instead.

Input Schema

Name	Required	Description
`cc`	No	Optional CC recipients, comma-separated for multiple
`to`	No	Optional recipient email address(es), comma-separated for multiple
`bcc`	No	Optional BCC recipients, comma-separated for multiple
`account`	Yes	Account name to use for the sender identity (e.g., "Work", "Oracle")
`subject`	No	Subject line for the draft (optional; defaults to empty)
`html_body`	No	Optional HTML body. If omitted but text_body is provided, a basic HTML wrapper is generated.
`text_body`	No	Optional plain-text body. If omitted but html_body is provided, a fallback plain body is generated.
`output_path`	No	Optional path for the generated `.eml` file (same protected-location rules as save_email_attachment; defaults to ~/Library/Caches/apple-mail-mcp/rich-drafts)
`from_address`	No	Optional sender address to stamp into the `.eml` `From:` header. Must be one of the account's configured email addresses. When omitted, Mail fills the account's default "Send new messages from" address on open.
`open_in_mail`	No	If True, open the generated `.eml` in Mail (default: True)
`save_as_draft`	No	Not currently supported. Mail opens a `.eml` as a read-only message viewer, not a compose object, so it can never be saved into Drafts this way. Passing True is reported honestly in the output rather than silently ignored; use `compose_email(mode="draft")` or `manage_drafts` for a real, sendable draft.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 schema fields changedv3.2.1Oct 20, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / account / description

Added value: +"Account name to use for the sender identity (e.g., \"Work\", \"Oracle\")"

removedInput schema / properties / account / title
```
Removed value: -"Account"
```

addedInput schema / properties / bcc / description

Added value: +"Optional BCC recipients, comma-separated for multiple"

removedInput schema / properties / bcc / title
```
Removed value: -"Bcc"
```

addedInput schema / properties / cc / description

Added value: +"Optional CC recipients, comma-separated for multiple"

removedInput schema / properties / cc / title
```
Removed value: -"Cc"
```

addedInput schema / properties / from_address / description

Added value: +"Optional sender address to stamp into the `.eml` `From:` header. Must be one of the account's configured email addresses. When omitted, Mail fills the account's default \"Send new messages from\" address on open."

removedInput schema / properties / from_address / title
```
Removed value: -"From Address"
```

addedInput schema / properties / html_body / description

Added value: +"Optional HTML body. If omitted but text_body is provided, a basic HTML wrapper is generated."

removedInput schema / properties / html_body / title
```
Removed value: -"Html Body"
```

addedInput schema / properties / open_in_mail / description

Added value: +"If True, open the generated `.eml` in Mail (default: True)"

removedInput schema / properties / open_in_mail / title
```
Removed value: -"Open In Mail"
```

addedInput schema / properties / output_path / description

Added value: +"Optional path for the generated `.eml` file (same protected-location\nrules as save_email_attachment; defaults to ~/Library/Caches/apple-mail-mcp/rich-drafts)"

removedInput schema / properties / output_path / title
```
Removed value: -"Output Path"
```

addedInput schema / properties / save_as_draft / description

Added value: +"Not currently supported. Mail opens a `.eml` as a read-only message\nviewer, not a compose object, so it can never be saved into Drafts this way.\nPassing True is reported honestly in the output rather than silently ignored;\nuse `compose_email(mode=\"draft\")` or `manage_drafts` for a real, sendable draft."

removedInput schema / properties / save_as_draft / title
```
Removed value: -"Save As Draft"
```

addedInput schema / properties / subject / description

Added value: +"Subject line for the draft (optional; defaults to empty)"

removedInput schema / properties / subject / title
```
Removed value: -"Subject"
```

addedInput schema / properties / text_body / description

Added value: +"Optional plain-text body. If omitted but html_body is provided, a fallback plain body is generated."

removedInput schema / properties / text_body / title
```
Removed value: -"Text Body"
```

addedInput schema / properties / to / description

Added value: +"Optional recipient email address(es), comma-separated for multiple"

removedInput schema / properties / to / title
```
Removed value: -"To"
```

removedInput schema / title

Removed value: -"create_rich_email_draftArguments"

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```

removedOutput schema / title

Removed value: -"create_rich_email_draftOutput"

addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed1 schema field changedv3.1.4Jun 3, 2026

addedInput schema / properties / from_address

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "From Address"
+}

First observedv3.1.0Apr 2, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the behavioral burden. It discloses that the result is unsent, that the artifact is a `.eml` file, that opening in Mail is optional, and warns about the AppleScript literal-markup pitfall — useful beyond structured fields. It omits permission requirements and the protected-location file rules, which are only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core action front-loaded and the differentiating rationale second. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the 100%-covered schema handles parameters. The description adequately frames the tool's purpose and safe-usage context for a file-writing, optionally-opening operation, though it stays silent on permissions and the caveat about save_as_draft lives in the schema rather than here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% across 11 parameters, so the schema fully documents recipients, bodies, paths, and flags. The description adds no parameter-level syntax or defaults beyond what the schema already states, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a rich-text email draft') and immediately explains the mechanism (generating an unsent `.eml` message, optionally opening it in Mail). The rationale about Mail reliably rendering `.eml` versus AppleScript storing literal markup distinguishes it from compose_email/manage_drafts paths.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states this is 'the preferred path for HTML or richly formatted emails,' giving a clear when-to-use condition. It stops short of naming the alternative tools (compose_email, manage_drafts) or stating when NOT to use it, so it's strong but not fully routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.