Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

Forward Email

forward_email

Forward an email to one or more recipients by searching for a subject keyword in a specified account and mailbox. Include CC/BCC and an optional message.

Instructions

Forward an email to one or more recipients.

Input Schema

Name	Required	Description	Default
`cc`	No	Optional CC recipients, comma-separated for multiple
`to`	Yes	Recipient email address(es), comma-separated for multiple
`bcc`	No	Optional BCC recipients, comma-separated for multiple
`account`	Yes	Account name (e.g., "Gmail", "Work")
`mailbox`	No	Mailbox to search in (default: "INBOX")	INBOX
`message`	No	Optional message to add before forwarded content
`from_address`	No	Optional sender address to use when forwarding. Must be one of the account's configured email addresses. When omitted, Mail uses the account's default "Send new messages from" setting.
`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.

Changed21 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 / 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 use when forwarding. 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 / mailbox / description
```
Added value: +"Mailbox to search in (default: \"INBOX\")"
```
- removedInput schema / properties / mailbox / title
```
Removed value: -"Mailbox"
```
- addedInput schema / properties / message / description
```
Added value: +"Optional message to add before forwarded content"
```
- removedInput schema / properties / message / title
```
Removed value: -"Message"
```
- 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"
```
- addedInput schema / properties / to / description
```
Added value: +"Recipient email address(es), comma-separated for multiple"
```
- removedInput schema / properties / to / title
```
Removed value: -"To"
```
- removedInput schema / title
```
Removed value: -"forward_emailArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"forward_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 behavioral burden, yet it says nothing about side effects. It does not state that this sends an irreversible outbound message, what happens when the subject keyword matches multiple emails, or whether the original attachments/content are preserved.

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?

The single sentence is front-loaded and has zero waste, but for an 8-parameter tool with required subject_keyword targeting it is thin, and the key selection mechanism is buried in the schema rather than surfaced up front.

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 no explanation, but for a mutation/send tool with zero annotations and an indirect addressing scheme (subject_keyword lookup) the description should clarify how the target email is chosen and what the send actually does. That context is entirely absent.

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 all 8 parameters are documented in the schema, including the subtle from_address constraint and the mailbox default. The description adds no parameter meaning beyond that, so the baseline of 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: forward an email to recipients. However, it does not reveal the non-obvious mechanism that the target email is located via a subject keyword search, nor does it distinguish this from siblings like reply_to_email or compose_email.

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 guidance and no mention of alternatives such as reply_to_email (respond to sender) or compose_email (new message). The agent is left to infer that 'forward' is the right choice.

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