Local MCP

Create Draft

create_draft

Saves an email to the Mail.app Drafts folder for the user to review and send manually — it never sends. Compose a new draft with to/subject and body or html_body, or save a reply draft with reply_to_message_id, reply_all, and body or html_body; the response names the Drafts mailbox and subject. A reply draft holds your text followed by a plain-text quote of the original ("On , wrote:" and the original's lines prefixed with > ), not Mail's styled quote, and in a reply draft html_body is converted to plain text. quoted_original in the response is true when the quote is there; it is false, with a note, when the original has no readable text. A reply draft's response includes threaded: true means the saved draft was read back and its headers reference the source message (it will appear inside the conversation); false means it saved WITHOUT threading headers (relay the warning to the user); "unconfirmed" means it could not be read back in time (e.g. Exchange sync lag). On a multi-account Mac, pass account (an account name from list_email_accounts) or from (a sender address) to place the draft in that account's Drafts; otherwise it lands in the default account. Attach files by passing attachments (comma-separated absolute file paths, e.g. a PDF quote) — they are attached to the saved draft. Use this for the cautious user who wants AI-composed mail but insists on sending it themselves. Requires confirm=true to actually save it — without it, returns a preview without touching Mail.app.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No	CC address(es), comma-separated.
`to`	No	Recipient address(es) for a new draft, comma-separated. May be left empty: the draft is saved without a recipient, to be added in Mail. Omit for a reply draft (uses reply_to_message_id).
`bcc`	No	BCC address(es), comma-separated.
`body`	No	Plain-text body of the draft.
`from`	No	Sender address — on a multi-account Mac, selects which account's Drafts to use. Alternative to `account`.
`account`	No	Account name (from list_email_accounts) whose Drafts folder receives the draft. Alternative to `from`.
`confirm`	No	Must be true to actually save the draft. Without it, returns a preview of the recipient/sender, subject, and that the body will be saved.	false
`subject`	No	Subject line for a new draft. Ignored for reply drafts (they inherit the original subject).
`html_body`	No	HTML body of the draft. Takes precedence over `body` when both are given.
`reply_all`	No	For a reply draft, include all original recipients (reply-all) instead of just the sender.	false
`attachments`	No	Files to attach, as comma-separated absolute paths (e.g. a PDF).
`reply_to_message_id`	No	Message id (from list_emails/search_emails) to draft a reply to, instead of a new message.

Output Schema

TableJSON Schema

Name	Required	Description
`to`	No
`from`	No
`kind`	No
`account`	No
`mailbox`	No
`subject`	No
`attachments`	No
`saved_draft`	No
`quoted_original`	No	Reply drafts only: true when the draft holds your text followed by a plain-text quote of the original.
`attachments_failed`	No
`reply_to_message_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / to / description

Previous value: -"Recipient address(es) for a new draft, comma-separated. Omit for a reply draft (uses reply_to_message_id)."New value: +"Recipient address(es) for a new draft, comma-separated. May be left empty: the draft is saved without a recipient, to be added in Mail. Omit for a reply draft (uses reply_to_message_id)."

addedOutput schema / properties / quoted_original

Added value: +{
+  "description": "Reply drafts only: true when the draft holds your text followed by a plain-text quote of the original.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 7, 2026
- addedOutput schema / properties / mailbox
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 27, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": "false",
+  "description": "Must be true to actually save the draft. Without it, returns a preview of the recipient/sender, subject, and that the body will be saved.",
+  "type": "boolean"
+}

Changed11 schema fields changedAug 4, 2026

addedInput schema / properties / account / description

Added value: +"Account name (from list_email_accounts) whose Drafts folder receives the draft. Alternative to `from`."

addedInput schema / properties / attachments / description

Added value: +"Files to attach, as comma-separated absolute paths (e.g. a PDF)."

addedInput schema / properties / bcc / description

Added value: +"BCC address(es), comma-separated."

addedInput schema / properties / body / description
```
Added value: +"Plain-text body of the draft."
```

addedInput schema / properties / cc / description

Added value: +"CC address(es), comma-separated."

addedInput schema / properties / from / description

Added value: +"Sender address — on a multi-account Mac, selects which account's Drafts to use. Alternative to `account`."

addedInput schema / properties / html_body / description

Added value: +"HTML body of the draft. Takes precedence over `body` when both are given."

addedInput schema / properties / reply_all / description

Added value: +"For a reply draft, include all original recipients (reply-all) instead of just the sender."

addedInput schema / properties / reply_to_message_id / description

Added value: +"Message id (from list_emails/search_emails) to draft a reply to, instead of a new message."

addedInput schema / properties / subject / description

Added value: +"Subject line for a new draft. Ignored for reply drafts (they inherit the original subject)."

addedInput schema / properties / to / description

Added value: +"Recipient address(es) for a new draft, comma-separated. Omit for a reply draft (uses reply_to_message_id)."

Changed3 schema fields changedJul 4, 2026

addedInput schema / properties / attachments
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / attachments

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / attachments_failed

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedJun 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses the plain-text quote format ('On <date>, <sender> wrote:' with '> ' prefixes), that html_body is downgraded to plain text in replies, the meaning of quoted_original, and the three-state threaded value including a relay-the-warning instruction. The confirm=true gate (preview without it) is a genuinely important behavioral disclosure for a mutation tool.

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

Conciseness4/5

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

Front-loaded with the key constraint ('never sends') and organized around new vs reply flows, but it is a dense multi-sentence block and some response-field detail could be trimmed given an output schema exists. Every sentence still carries substantive information.

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

Completeness5/5

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

For a 12-parameter tool with an output schema, the description covers the decision paths (new vs reply), the confirm gate, account targeting, attachments, and the threading caveats. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it groups parameters into new-draft vs reply-draft usage, clarifies account-vs-from as alternatives, notes subject is ignored in replies, and specifies the attachments path format. Only minor syntax detail is left to the schema.

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 (saves a draft) and resource (Mail.app Drafts folder), and immediately differentiates from send_email/reply_email by asserting 'it never sends.' An agent can tell it apart from the send siblings without opening either schema.

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?

Gives clear context: new draft via to/subject/body vs reply draft via reply_to_message_id/reply_all, plus the cautious-user scenario. It does not name send_email or reply_email as the explicit alternatives for when the user actually wants to send, so the routing is implied rather than stated.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.