apple-mail-mcp

Overview Schema Source Related Servers Discussions Admin

Send an email

send_email

Compose and send standards-correct MIME emails through your chosen Apple Mail identity, with optional Cc, Bcc, and attachments.

Instructions

Compose standards-correct MIME and send it through the selected identity.

Input Schema

TableJSON Schema

Name	Required	Description
`cc`	No	Optional comma-separated Cc recipients.
`to`	Yes	Comma-separated primary recipients, including optional display names.
`bcc`	No	Optional comma-separated Bcc recipients.
`body`	Yes	Plain-text email content; paragraph breaks are preserved.
`subject`	Yes	Email subject line.
`attachments`	No	Optional list of local file paths, one path per item.
`from_identity`	No	Configured sending identity; omit it to use the default.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.0Sep 13, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "attachments": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "bcc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "bootstrapped": {
-        "type": "boolean"
-      },
-      "cc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "error": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "message_id": {
-        "type": "string"
-      },
-      "ok": {
-        "type": "boolean"
-      },
-      "subject": {
-        "type": "string"
-      },
-      "to": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "ok",
-      "message_id",
-      "to",
-      "cc",
-      "bcc",
-      "subject",
-      "attachments",
-      "bootstrapped",
-      "error"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "error": {
-        "type": "string"
-      },
-      "fix": {
-        "type": "string"
-      },
-      "ok": {
-        "const": false
-      },
-      "operation_id": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "ok",
-      "code",
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "accepted": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "attachments": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "bcc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "bootstrapped": {
+        "type": "boolean"
+      },
+      "cc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "message_id": {
+        "type": "string"
+      },
+      "ok": {
+        "type": "boolean"
+      },
+      "refused": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "subject": {
+        "type": "string"
+      },
+      "to": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "ok",
+      "message_id",
+      "to",
+      "cc",
+      "bcc",
+      "subject",
+      "attachments",
+      "bootstrapped",
+      "error",
+      "accepted",
+      "refused",
+      "code"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "fix": {
+        "type": "string"
+      },
+      "ok": {
+        "const": false
+      },
+      "operation_id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "code",
+      "error"
+    ],
+    "type": "object"
+  }
+]

First observedv0.1.0Aug 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds a modest detail about MIME composition quality but omits consequences the agent would care about: that sending is irreversible, that repeated calls produce duplicate mail, and whether a copy is retained in Sent.

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?

A single front-loaded sentence with no filler, which is well sized for the tool. The wording is slightly cryptic ('standards-correct MIME', 'selected identity') rather than plainly informative, keeping it short of a 5.

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?

An output schema exists, so return values need no explanation, and the annotations carry the safety profile. For a straightforward send operation with fully described parameters, the description supplies enough to invoke the tool correctly; the remaining gaps (usage routing, irreversibility) are shared with the sibling set rather than blocking correct invocation.

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 every parameter (to, cc, bcc, body, subject, attachments, from_identity) is already documented in the schema. The description's only parameter-relevant content is the vague reference to 'the selected identity', which adds no syntax or format detail beyond what the schema provides, so the 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 ('send' + email) and adds the mechanism ('compose standards-correct MIME'). However, it does not differentiate from close siblings such as reply_email, schedule_email, or create_draft, so an agent cannot tell from the description alone which send path applies to a reply or a scheduled message.

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 or when-not-to-use guidance and no named alternative. The phrase 'through the selected identity' hints that from_identity matters, but nothing tells the agent to prefer this over create_draft, schedule_email, or reply_email for the corresponding scenarios.

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