Apple Mail MCP Server

Overview Schema Source Related Servers Discussions Admin

send_email

Compose and send an email directly from Apple Mail, specifying recipients, subject, body, attachments, and optional CC/BCC fields.

Instructions

Send a new email immediately.

Convenience wrapper over create_draft with send_now=True.

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": {
      "to": "<to>",
      "subject": "<subject>"
    },
    "name": "send_email"
  }
}

Input Schema

Name	Required	Description
`cc`	No	CC recipients.
`to`	Yes	List of recipient email addresses.
`bcc`	No	BCC recipients.
`body`	No	Plain text body.
`subject`	Yes	Email subject.
`from_account`	No	Mail.app account name or UUID. None = Mail default.
`attachment_paths`	No	List of local file paths to attach.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.2Aug 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description accurately describes the side effect (sending an email) without contradictions. Annotations already indicate it's a write operation and not idempotent, so the description doesn't need to restate that. It adds no misleading information.

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?

The description is exceptionally concise: two short sentences that convey the essence of the tool. It includes the primary action, the immediacy, and the relationship to create_draft without any superfluous words.

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

Completeness4/5

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

The description is complete for the tool's purpose. It clearly states what the tool does and its relationship to a sibling tool. Since an output schema exists, return values need not be explained. No critical information is missing.

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?

The description does not elaborate on any parameters, but the input schema provides full descriptions for all seven parameters with 100% coverage. Per the rubric, a high coverage warrants a baseline score of 3, and the description adds no additional meaning.

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 the action: 'Send a new email immediately.' It also distinguishes itself from create_draft by explicitly noting it is a convenience wrapper with send_now=True, which removes ambiguity about its purpose compared to related tools.

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?

The description implies when to use it vs. create_draft by presenting it as a convenience wrapper that sends immediately, but it doesn't explicitly contrast with other alternatives like reply or forward. It provides enough context for an agent to infer the appropriate use case.

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