apple-mail-mcp

by parasxos

Overview Schema Source Related Servers Discussions Admin

Python

Local

Schedule an email

schedule_email

Queue an email for delivery at a chosen time, either locally or through Exchange.

Instructions

Freeze an email now and schedule local or Exchange-side delivery.

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.
`send_at`	Yes	Delivery time in ISO-8601; a timestamp without an offset is local time.
`subject`	Yes	Email subject line.
`references`	No	Optional References header of the message being answered; in_reply_to is appended to it.
`attachments`	No	Optional list of local file paths, one path per item.
`in_reply_to`	No	Optional Message-ID of the message being answered, so the mail threads as a reply.
`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.

Changed2 schema fields changedv1.8.2Oct 1, 2026

addedInput schema / properties / in_reply_to

Added value: +{
+  "default": "",
+  "description": "Optional Message-ID of the message being answered, so the mail threads as a reply.",
+  "title": "In Reply To",
+  "type": "string"
+}

addedInput schema / properties / references

Added value: +{
+  "default": "",
+  "description": "Optional References header of the message being answered; in_reply_to is appended to it.",
+  "title": "References",
+  "type": "string"
+}

Changed1 schema field changedv1.6.0Sep 13, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "attachments": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "attempts": {
-        "type": "integer"
-      },
-      "bcc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "cc": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "created_at": {
-        "type": "string"
-      },
-      "delivered_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "executor": {
-        "type": "string"
-      },
-      "graph_draft_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "type": "string"
-      },
-      "identity": {
-        "type": "string"
-      },
-      "last_error": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "message_id": {
-        "type": "string"
-      },
-      "next_attempt_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "ok": {
-        "const": true
-      },
-      "send_at": {
-        "type": "string"
-      },
-      "status": {
-        "type": "string"
-      },
-      "subject": {
-        "type": "string"
-      },
-      "to": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "ok",
-      "id",
-      "send_at",
-      "created_at",
-      "to",
-      "cc",
-      "bcc",
-      "subject",
-      "attachments",
-      "message_id",
-      "status",
-      "attempts",
-      "next_attempt_at",
-      "last_error",
-      "delivered_at",
-      "identity",
-      "executor",
-      "graph_draft_id"
-    ],
-    "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"
+      },
+      "attempts": {
+        "type": "integer"
+      },
+      "bcc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "cc": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "claimed_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "code": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "created_at": {
+        "type": "string"
+      },
+      "delivered_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "executor": {
+        "type": "string"
+      },
+      "graph_draft_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "identity": {
+        "type": "string"
+      },
+      "last_error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "message_id": {
+        "type": "string"
+      },
+      "next_attempt_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "ok": {
+        "const": true
+      },
+      "refused": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "send_at": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "subject": {
+        "type": "string"
+      },
+      "to": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "ok",
+      "id",
+      "send_at",
+      "created_at",
+      "to",
+      "cc",
+      "bcc",
+      "subject",
+      "attachments",
+      "message_id",
+      "status",
+      "attempts",
+      "next_attempt_at",
+      "last_error",
+      "delivered_at",
+      "identity",
+      "executor",
+      "graph_draft_id",
+      "accepted",
+      "refused",
+      "code",
+      "claimed_at"
+    ],
+    "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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact: content is 'frozen' now, implying attachments (local file paths) and body are resolved at schedule time, not delivery time. It says nothing about cancellation, permission requirements, or what happens if delivery fails.

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?

A single front-loaded sentence with the core action first and the delivery-mode nuance trailing. Zero filler, no restatement of the title or parameter list.

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

Completeness3/5

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

For a 10-parameter, non-idempotent, open-world mutation tool, one sentence is thin. The output schema means return values needn't be explained and the 100%-covered schema handles parameters, but the description omits the scheduling lifecycle (how to view or cancel scheduled mail) and the timing consequence of 'freeze now' for attachment paths.

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% across all 10 parameters, so the schema already carries the semantics (Cc/Bcc format, ISO-8601 send_at with local-time default, reply threading via in_reply_to/references, attachment paths). The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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 ('schedule ... delivery') and adds the unusual but informative 'freeze an email now', which tells the agent the message content is captured at scheduling time rather than send time. It does not explicitly name the sibling it contrasts with (send_email for immediate delivery, create_draft for unsent drafts), so sibling differentiation is only implied.

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 alternative named, despite the presence of send_email, create_draft, list_scheduled and cancel_scheduled as siblings. The only usage signal is the incidental phrase 'local or Exchange-side delivery', which hints at two scheduling modes but never tells the agent how to choose or what to expect.

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