A skill your agent uses when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail.

MITAuto-check passedProductivity & Automation

Install Applescript Mail

skills CLI
$ npx skills add s-morgan-jeffries/apple-mail-fast-mcp --skill applescript-mail -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install s-morgan-jeffries/apple-mail-fast-mcp applescript-mail --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/s-morgan-jeffries/apple-mail-fast-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/applescript-mail .claude/skills/applescript-mail && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
applescript-mail
GitHub stars
104
Token cost
~2.5k tokens
SKILL.md length
996 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail.

  • Works in 7 steps: No scheduled sending — Mail.app has no… → Thread reconstruction is possible but… → Rule management is partial — Rules are… → …
  • Debugging ANY AppleScript that interacts with Apple Mail
  • SKILL.md covers Emitting JSON from AppleScript, Gmail Label-Based System, Message ID Lookup and String Escaping, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Applescript Mail is an agent skill from s-morgan-jeffries/apple-mail-fast-mcp. Use when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail. Also use when encountering AppleScript errors, unexpected Mail.app behavior, when adding new connector methods, or when debugging JSON output from ASObjC. Covers string escaping, attachment handling, Gmail compatibility, message ID lookup patterns, NSJSONSerialization gotchas, and known Mail.app automation limitations.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Email management and App automation through connectors. It works with Gmail. The repository describes itself as: 🤖 MCP server for Apple Mail - Manage emails with AI using Claude Desktop. Search, send, organize mail with natural language. The licence is MIT.

When your agent uses it

  • Debugging ANY AppleScript that interacts with Apple Mail
  • Encountering AppleScript errors
  • Unexpected Mail.app behavior
  • Adding new connector methods

Example prompts

  • “/applescript-mail”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. No scheduled sending — Mail.app has no AppleScript support for delayed/scheduled sends
  2. Thread reconstruction is possible but not native — Mail.app has no thread or conversation class. Reconstruct threads by reading headers of…
  3. Rule management is partial — Rules are readable (rules collection, name, enabled, conditions/actions), but have no stable id and must be…
  4. No smart mailbox access — Smart mailboxes are not exposed to AppleScript
  5. Rich text body — content of message returns plain text; HTML body requires alternate approach
  6. Read receipt — Cannot request or detect read receipts
  7. Draft management — Creating drafts is possible but managing them is limited

What it can do on your machine

Read from SKILL.md and the folder at commit ed0cfbc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are applescript and python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Applescript Mail loads about 2.5k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 996 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from s-morgan-jeffries/apple-mail-fast-mcp at commit ed0cfbc, republished under its MIT licence (© s-morgan-jeffries). 996 words, ~2,527 tokens.

Download SKILL.mdSave it as .claude/skills/applescript-mail/SKILL.md (or your agent's skills folder).
name
applescript-mail
description
Use when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail. Also use when encountering AppleScript errors, unexpected Mail.app behavior, when adding new connector methods, or when debugging JSON output from ASObjC. Covers string escaping, attachment handling, Gmail compatibility, message ID lookup patterns, NSJSONSerialization gotchas, and known Mail.app automation limitations.

AppleScript + Apple Mail Patterns

Emitting JSON from AppleScript

Scripts emit JSON via ASObjC + NSJSONSerialization (not pipe-delimited text). Use the _wrap_as_json_script(body) helper in mail_connector.py and parse responses with parse_applescript_json(result) from utils.py.

Tell-block contract: the body passed to _wrap_as_json_script must contain a tell application "Mail" ... end tell block and assign the final value to a variable named resultData (list, record, or scalar).

Record key gotcha — always quote name: Use |name|:(name of acc), never name:(name of acc). The bare form collides with NSObject's name selector and the key is silently dropped during NSDictionary conversion, leaving records without their name field.

missing value gotcha: NSJSONSerialization rejects missing value. For optional properties (e.g., email addresses of an account with none, unread count on some mailboxes), coerce before building the record:

applescript
set accEmails to email addresses of acc
if accEmails is missing value then set accEmails to {}

Error propagation: Do NOT wrap the tell-body in try / on error when you want typed exceptions (MailAccountNotFoundError, MailMessageNotFoundError, etc.). Let AppleScript errors bubble via stderr — _run_applescript maps them to the right exception type.

Gmail Label-Based System

Gmail doesn't support standard IMAP move operations. The update_message tool has a gmail_mode parameter (when used with destination_mailbox):

python
# Standard IMAP (Exchange, iCloud, etc.)
move message to destination_mailbox

# Gmail mode (copy + delete)
duplicate message to destination_mailbox
delete message  # Removes from source label

Bug story: Early versions silently failed when moving Gmail messages. The move appeared to succeed but the message stayed in the source mailbox. gmail_mode was added to handle this.

When to use: Always expose gmail_mode as an optional parameter on any tool that moves or archives messages.

Message ID Lookup

Finding a specific message by ID requires searching across accounts and mailboxes:

applescript
tell application "Mail"
    set allAccounts to every account
    repeat with acct in allAccounts
        set allMailboxes to every mailbox of acct
        repeat with mbox in allMailboxes
            set msgs to (messages of mbox whose id is targetId)
            if (count of msgs) > 0 then
                return first item of msgs
            end if
        end repeat
    end repeat
end tell

Performance: This is O(accounts × mailboxes). For users with many accounts, this can be slow. The whose clause makes it tolerable but not fast.

Optimization: If the caller knows the account and mailbox, always accept them as optional parameters to narrow the search.

String Escaping

Always use escape_applescript_string() for user-provided text:

python
# In utils.py — escapes backslashes first, then double quotes
def escape_applescript_string(s: str) -> str:
    return s.replace("\\", "\\\\").replace('"', '\\"')

Bug story: Unescaped quotes in email subjects caused AppleScript blocks to fail silently. The error appears as a generic "Can't make" error in stderr with no indication of the actual cause.

Rule: Every string interpolated into AppleScript MUST go through escape_applescript_string(). No exceptions. Check via check_applescript_safety.sh.

Dates: never use a date "..." literal

AppleScript parses date-string literals against the user's locale, and gets it wrong silently:

applescript
date "2026-05-28"           --> year 12196
date "2026-08-09 11:03:51"  --> Wednesday, October 8, 12177

Neither raises. Nothing warns. A filter built on one of these just quietly matches nothing — and because the surrounding code behaves correctly, the bug is invisible above the AppleScript boundary.

Bug story (#436): a date literal bounded a message-search window. The window was ~10,000 years off, so it matched nothing, and the failure surfaced as a clean, plausible MailAnchorLookupIncompleteError for a message sitting at index 1 of the INBOX. Cost a full integration cycle. The trap had already been documented — in a helper docstring inside a 6,000-line module, which is not where anyone writing new AppleScript looks. Hence this section.

Always build dates from components via _construct_as_date_var() in mail_connector.py:

python
_construct_as_date_var("targetDate", 2026, 8, 9, 39831)  # 39831 = 11:03:51

which emits:

applescript
set targetDate to current date
set day of targetDate to 1        -- FIRST: see below
set year of targetDate to 2026
set month of targetDate to 8
set day of targetDate to 9
set time of targetDate to 39831   -- seconds since midnight

Why set day to 1 comes first: if current date is the 31st and you set month to a 30-day month, AppleScript rolls into the next month. Resetting the day first makes the sequence safe for every date.

Rule: every date in generated AppleScript goes through _construct_as_date_var(). check_applescript_safety.sh (Check 6) fails the build on a date "..." literal in src/. If you are documenting the trap rather than committing it, wrap the example in backticks — that is how the check distinguishes prose from code.

Attachment Handling

Attachments use POSIX file references:

applescript
-- Sending attachments
set theAttachment to POSIX file "/Users/user/file.pdf"
make new attachment with properties {file name: theAttachment} at after the last paragraph

-- Saving attachments
save attachment theAttach in POSIX file "/Users/user/Downloads/"

Path conversion: Python Path objects → .as_posix() → AppleScript POSIX file "...".

Security: Always validate:

  • File exists before sending
  • Directory exists before saving
  • No path traversal (.. in path)
  • Extension not in blocklist (.exe, .bat, .sh, .app, etc.)
  • Size under 25MB limit
Show full SKILL.md (401 more words)Show less

whose Clause Filtering

Use AppleScript whose clauses for server-side filtering instead of fetching all messages:

applescript
-- GOOD: Server-side filter (fast)
set msgs to (messages of mbox whose sender contains "user@example.com")

-- BAD: Fetch all then filter in Python (slow)
set msgs to every message of mbox
-- then filter in Python

Combine clauses for multi-field search:

applescript
messages whose sender contains "user" and subject contains "report"

Limitation: whose clauses don't support OR logic well. For OR conditions, use multiple whose queries and merge results in Python.

Known Mail.app Automation Limitations

  1. No scheduled sending — Mail.app has no AppleScript support for delayed/scheduled sends

  2. Thread reconstruction is possible but not native — Mail.app has no thread or conversation class. Reconstruct threads by reading headers of msg for in-reply-to, references, and matching against message id of msg (the RFC 822 header value) across candidate messages. See get_thread in mail_connector.py.

    whose message id is "X" is NOT indexed, and AppleScript runs on Mail's UI thread — so it loads every message in the mailbox and freezes the app, not merely slowly (measured: 33,569 messages in one INBOX, 62,085 in Gmail's All Mail). The _run_applescript timeout does not rescue Mail; it kills our osascript client while Mail keeps grinding.

    Resolve an RFC Message-ID by IMAP first — SEARCH HEADER Message-ID is server-indexed (measured 0.14s over 61,880 messages) and returns the arrival date — then binary-search the mailbox by that date. Messages enumerate strictly newest-first with cheap positional access, so that is ~log₂(n) property reads. See find_message_by_message_id (#432/#434). Mail's numeric id is indexed, so whose id is N stays instant and needs none of this.

  3. Rule management is partial — Rules are readable (rules collection, name, enabled, conditions/actions), but have no stable id and must be addressed positionally or by non-unique name. Mutation paths (creating, updating, deleting) are more complex and not yet implemented.

  4. No smart mailbox access — Smart mailboxes are not exposed to AppleScript

  5. Rich text body — content of message returns plain text; HTML body requires alternate approach

  6. Read receipt — Cannot request or detect read receipts

  7. Draft management — Creating drafts is possible but managing them is limited

Error Handling Pattern

applescript
try
    -- operation
    return "result_data"
on error errMsg
    return "ERROR: " & errMsg
end try

Python-side parsing:

python
if result.startswith("ERROR:"):
    raise MailAppleScriptError(result[7:])

stderr-based errors are caught in _run_applescript() and routed to typed exceptions:

  • "Can't get account" → MailAccountNotFoundError
  • "Can't get mailbox" → MailMailboxNotFoundError
  • "Can't get message" → MailMessageNotFoundError
  • Everything else → MailAppleScriptError

Checklist: New AppleScript Operation

  1. All user strings escaped with escape_applescript_string()
  2. All inputs sanitized with sanitize_input()
  3. Any dates built via _construct_as_date_var(), never a date "..." literal
  4. Error handling with try/on error in AppleScript
  5. Timeout considered (complex operations may need > 60s)
  6. Integration test written against real Mail.app
  7. check_applescript_safety.sh passes
  8. Gmail compatibility considered (does this operation work with labels?)

© s-morgan-jeffries, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/applescript-mail of s-morgan-jeffries/apple-mail-fast-mcp.

Open the folder on GitHubat commit ed0cfbc

Compare with similar skills

Applescript Mail next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Applescript Mail compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Applescript Mail this skills-morgan-jeffries/apple-mail-fast-mcp104—~2.5kAutomated safety check: PassMIT
Connect Apps with ComposioComposioHQ/awesome-claude-skills77k3 repos~557Automated safety check: PassNone
Composio Cloud Toolsquarqlabs/argus279—~543Automated safety check: PassApache-2.0
Gmail Automationdavepoon/buildwithclaude3.6k4 repos~2.7kAutomated safety check: PassMIT
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0
Google Workspace CLIlaude-institute/headlong1.2k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Connect Apps with Composio

    ComposioHQ/awesome-claude-skills

    Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.

    77k GitHub starsUsed in 3 repos~557 tokens
    Productivity & AutomationAuto-check passed
  • Composio Cloud Tools

    quarqlabs/argus

    Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.

    279 GitHub stars~543 tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed
  • Gmail Automation

    davepoon/buildwithclaude

    Automate Gmail tasks via Rube MCP (Composio): send/reply, search, labels, drafts, attachments.

    3.6k GitHub starsUsed in 4 repos~2.7k tokens
    Productivity & AutomationAuto-check passed
  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 15 days ago
    Productivity & AutomationAuto-check passed
  • Google Workspace CLI

    laude-institute/headlong

    Drives Google Drive, Gmail, Calendar, Sheets, Docs and Chat from the shell with the gws CLI, including its sign-in, flags, helper commands and safety rules.

    1.2k GitHub stars~1.2k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check: notes

More from s-morgan-jeffries/apple-mail-fast-mcp

  • API Design

    s-morgan-jeffries/apple-mail-fast-mcp

    Use BEFORE adding any new tool, parameter, or endpoint to the Apple Mail MCP server.

    104 GitHub stars~876 tokensUpdated 29 days ago
    Auto-check passed
  • Integration Testing

    s-morgan-jeffries/apple-mail-fast-mcp

    A skill your agent uses when setting up, running, or debugging integration tests against real Apple Mail.

    104 GitHub stars~1.2k tokensUpdated 29 days ago
    Auto-check passed
  • Performance Patterns

    s-morgan-jeffries/apple-mail-fast-mcp

    A skill your agent uses when optimizing Apple Mail MCP operations, diagnosing slow queries, adding new filtering logic, or modifying how data is fetched from Mail.app.

    104 GitHub stars~1.5k tokensUpdated 29 days ago
    Auto-check passed
  • Release

    s-morgan-jeffries/apple-mail-fast-mcp

    A skill your agent uses when the user wants to release a new version.

    104 GitHub stars~1.3k tokensUpdated 29 days ago
    Auto-check passed

Works with

Questions about Applescript Mail

What does Applescript Mail do?

A skill your agent uses when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail. Applescript Mail is an agent skill from s-morgan-jeffries/apple-mail-fast-mcp. Use when writing, modifying, or debugging ANY AppleScript that interacts with Apple Mail.

When should I use Applescript Mail?

Applescript Mail fits situations like: debugging ANY AppleScript that interacts with Apple Mail; encountering AppleScript errors; unexpected Mail.app behavior; adding new connector methods.

How do I install Applescript Mail in Claude Code?

Run `npx skills add s-morgan-jeffries/apple-mail-fast-mcp --skill applescript-mail -a claude-code`. Or copy the skill folder (.claude/skills/applescript-mail in s-morgan-jeffries/apple-mail-fast-mcp) into .claude/skills/applescript-mail in your project. Claude Code loads it when a task matches its description.

How do I install Applescript Mail in Codex?

Run `npx skills add s-morgan-jeffries/apple-mail-fast-mcp --skill applescript-mail -a codex`. Or copy the skill folder (.claude/skills/applescript-mail in s-morgan-jeffries/apple-mail-fast-mcp) into .agents/skills/applescript-mail in your project. Codex loads it when a task matches its description.

Can I use Applescript Mail in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add s-morgan-jeffries/apple-mail-fast-mcp --skill applescript-mail -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/applescript-mail, .gemini/skills/applescript-mail, .github/skills/applescript-mail and .opencode/skills/applescript-mail in your project.

What does Applescript Mail need to run?

SKILL.md names no scripts, command-line tools or credentials: Applescript Mail is instructions for the agent only. Our summary lists: Python 3.

Does Applescript Mail access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Applescript Mail safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Applescript Mail use?

Applescript Mail is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Applescript Mail use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Applescript Mail?

Skills that share tags, products or a category with Applescript Mail: Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Composio Cloud Tools (quarqlabs/argus, 279 stars), Gmail Automation (davepoon/buildwithclaude, 3.6k stars) and Openloomi Connectors (melandlabs/openloomi, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Applescript Mail?

s-morgan-jeffries (a GitHub user) maintains it in s-morgan-jeffries/apple-mail-fast-mcp, which has 104 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 9, 2026.

Source: s-morgan-jeffries/apple-mail-fast-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.