Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

export_emails

Export emails from Apple Mail accounts to files on disk for backup or analysis. Supports single email or entire mailbox export in TXT or HTML format.

Instructions

Export emails to files for backup or analysis.

Args: account: Account name (e.g., "Gmail", "Work") scope: Export scope: "single_email" (requires subject_keyword) or "entire_mailbox" subject_keyword: Keyword to find email (required for single_email) mailbox: Mailbox to export from (default: "INBOX") save_directory: Directory to save exports (default: "~/Desktop") format: Export format: "txt", "html" (default: "txt") max_emails: Maximum number of emails to export for entire_mailbox (default: 1000, safety cap)

Returns: Confirmation message with export location

User Preferences: {"workflow": "default", "notifications": "enabled"}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "scope": "<scope>"
    },
    "name": "export_emails"
  }
}

Input Schema

Name	Required	Default
`scope`	Yes
`format`	No	txt
`account`	Yes
`mailbox`	No	INBOX
`max_emails`	No
`save_directory`	No	~/Desktop
`subject_keyword`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.6.1Jul 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Although no annotations are provided, the description discloses key behaviors: it exports to files, provides a safety cap (max_emails: 1000), defaults for format and directory, and clarifies required parameters for scopes. It does not mention error handling or authentication, but the core behavior is well-covered.

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?

The description is a structured docstring with a brief sentence, then bulleted args, and a returns line. It is concise but includes the 'User Preferences' line which may be extraneous. Overall, it is well-organized and easy to scan.

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?

Given the tool's complexity (7 parameters, two scopes) and the presence of an output schema (which likely details the return), the description covers all necessary aspects: parameter meanings, defaults, constraints, and a high-level return description. It is complete for an agent to use correctly.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each parameter: account (with examples), scope (enum values and constraint), subject_keyword (required for single_email), mailbox (default), save_directory (default), format (enum, default), max_emails (purpose and default). This makes all parameters understandable.

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?

The description clearly states 'Export emails to files for backup or analysis', specifying the verb (export), resource (emails), and purpose (backup or analysis). This distinguishes it from sibling tools like compose_email, delete_emails, etc.

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 explicit guidance is provided on when to use this tool versus alternatives. The description lacks context such as 'Use this instead of list_inbox_emails when you need file output' or 'Not for immediate viewing'.

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