Apple Mail MCP Server

by patrickfreyer

Overview Schema Source Related Servers Discussions Admin

Python

Local

Reply To Email

reply_to_email

Reply to an email by matching a subject keyword; send it, save as draft, or open compose for review in Apple Mail.

Instructions

Reply to an email matching a subject keyword.

Input Schema

Name	Required	Description
`cc`	No	Optional CC recipients, comma-separated for multiple
`bcc`	No	Optional BCC recipients, comma-separated for multiple
`mode`	No	Delivery mode — "send" (send immediately), "draft" (save silently), or "open" (open compose window for review). Overrides send parameter when set.
`send`	No	If True (default), send immediately; if False, save as draft. Ignored if mode is set.
`account`	Yes	Account name (e.g., "Gmail", "Work")
`body_html`	No	Optional HTML body for rich formatting (bold, headings, links, colors). When provided, the reply is pasted as HTML. The plain 'reply_body' field is still required as fallback text.
`reply_body`	Yes	The body text of the reply
`attachments`	No	Optional file paths to attach, comma-separated for multiple (e.g., "/path/to/file1.png,/path/to/file2.pdf")
`from_address`	No	Optional sender address to use for this reply. Must be one of the account's configured email addresses. When omitted, Mail uses the account's default "Send new messages from" setting.
`reply_to_all`	No	If True, reply to all recipients; if False, reply only to sender (default: False)
`subject_keyword`	Yes	Keyword to search for in email subjects

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 (e.g., \"Gmail\", \"Work\")"

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

addedInput schema / properties / attachments / description

Added value: +"Optional file paths to attach, comma-separated for multiple (e.g., \"/path/to/file1.png,/path/to/file2.pdf\")"

removedInput schema / properties / attachments / title
```
Removed value: -"Attachments"
```

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 / body_html / description

Added value: +"Optional HTML body for rich formatting (bold, headings, links, colors). When provided, the reply is pasted as HTML. The plain 'reply_body' field is still required as fallback text."

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

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 use for this reply. 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 / mode / description

Added value: +"Delivery mode — \"send\" (send immediately), \"draft\" (save silently), or \"open\" (open compose window for review). Overrides send parameter when set."

removedInput schema / properties / mode / title
```
Removed value: -"Mode"
```
addedInput schema / properties / reply_body / description
```
Added value: +"The body text of the reply"
```
removedInput schema / properties / reply_body / title
```
Removed value: -"Reply Body"
```

addedInput schema / properties / reply_to_all / description

Added value: +"If True, reply to all recipients; if False, reply only to sender (default: False)"

removedInput schema / properties / reply_to_all / title
```
Removed value: -"Reply To All"
```

addedInput schema / properties / send / description

Added value: +"If True (default), send immediately; if False, save as draft. Ignored if mode is set."

removedInput schema / properties / send / title
```
Removed value: -"Send"
```
addedInput schema / properties / subject_keyword / description
```
Added value: +"Keyword to search for in email subjects"
```
removedInput schema / properties / subject_keyword / title
```
Removed value: -"Subject Keyword"
```

removedInput schema / title

Removed value: -"reply_to_emailArguments"

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

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about the fact that this is a side-effectful send operation by default (send=true), that it can silently save a draft, or what happens if multiple emails match the subject keyword — all of which matter for a mutation tool with zero annotation coverage.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is structurally clean, but for an 11-parameter send operation this is under-specification rather than genuine conciseness — it omits information an agent needs rather than trimming noise.

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

Completeness2/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, but the description omits the critical context that this tool sends mail by default, may match multiple emails, and requires a configured account. For a high-complexity side-effectful tool with no annotations, the definition is not complete enough to call safely.

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%, so all 11 parameters are already documented in the schema (mode, send, reply_to_all, from_address, etc.). The description's only parameter-adjacent content, subject-keyword matching, merely repeats what the schema says, so 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?

States a specific verb and resource ("Reply to an email") plus the selection mechanism ("matching a subject keyword"), which is more precise than a name restatement. However it never distinguishes itself from close siblings like compose_email or forward_email, so an agent gets no help picking between them.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives (compose_email, forward_email, manage_drafts). The only implied usage is that the target email is identified by subject keyword, which is barely a usage condition.

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