Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

Manage Drafts

manage_drafts

List, create, send, open, or delete draft emails in Apple Mail across accounts; set recipients, subject, body, and sender, or locate drafts by subject.

Instructions

Manage draft emails - list, create, send, open, or delete drafts.

Input Schema

Name	Required	Description
`cc`	No	Optional CC recipients for create
`to`	No	Recipient email(s) for create (comma-separated)
`bcc`	No	Optional BCC recipients for create
`body`	No	Email body (required for create)
`action`	Yes	Action to perform: "list", "create", "send", "open", "delete". Use "open" to open a draft in a visible compose window for review before sending.
`account`	Yes	Account name (e.g., "Gmail", "Work")
`subject`	No	Email subject (required for create)
`from_address`	No	Optional sender address for new drafts (action="create"). Must be one of the account's configured email addresses. When omitted, Mail uses the account's default "Send new messages from" setting.
`draft_subject`	No	Subject keyword to find draft (required for send/open/delete)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv3.2.1Oct 20, 2026

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

addedInput schema / properties / account / description

Added value: +"Account name (e.g., \"Gmail\", \"Work\")"

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

addedInput schema / properties / action / description

Added value: +"Action to perform: \"list\", \"create\", \"send\", \"open\", \"delete\". Use \"open\" to open a draft in a visible compose window for review before sending."

removedInput schema / properties / action / title
```
Removed value: -"Action"
```

addedInput schema / properties / bcc / description

Added value: +"Optional BCC recipients for create"

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

addedInput schema / properties / body / description

Added value: +"Email body (required for create)"

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

addedInput schema / properties / cc / description

Added value: +"Optional CC recipients for create"

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

addedInput schema / properties / draft_subject / description

Added value: +"Subject keyword to find draft (required for send/open/delete)"

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

addedInput schema / properties / from_address / description

Added value: +"Optional sender address for new drafts (action=\"create\"). Must be one of the account's configured email addresses. When omitted, Mail uses the account's default \"Send new messages from\" setting."

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

addedInput schema / properties / subject / description

Added value: +"Email subject (required for create)"

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

addedInput schema / properties / to / description

Added value: +"Recipient email(s) for create (comma-separated)"

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

removedInput schema / title

Removed value: -"manage_draftsArguments"

removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
removedOutput schema / title
```
Removed value: -"manage_draftsOutput"
```
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

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does not meet it. It never states that 'send' is an irreversible outbound action, that 'delete' is destructive, whether deletions are recoverable, or what account/permission requirements apply. The action list merely repeats what the schema already enumerates.

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?

A single front-loaded sentence that states the resource first and the supported operations second, with no filler. Nothing could be cut without losing content.

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

Completeness3/5

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

The rich input schema and the presence of an output schema mean the description needn't explain parameters or return values, so it is not badly deficient. But for a nine-parameter, five-action mutation tool with zero annotations, the description should at minimum disambiguate against the compose/create siblings and flag the irreversible actions.

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 description coverage is 100% and the schema itself is unusually rich, including the from_address fallback behavior and the create/send/open/delete requirements. The description adds no syntax, format, or conditional meaning beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description names the resource (draft emails) and enumerates the five operations it supports (list, create, send, open, delete), so an agent knows exactly what the tool covers. However, it never differentiates itself from overlapping siblings such as create_rich_email_draft or compose_email, which also produce or send mail, so the boundary is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance in the description. The agent is not told when to pick this tool over compose_email, create_rich_email_draft, or reply_to_email, nor that 'send' should follow an 'open' review. The only routing hint ('use open to review before sending') lives in the schema's action description, not here.

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