Apple Mail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JXA_MAIL_DEFAULT_ACCOUNT | No | Set the default Apple Mail account to use for queries (e.g., 'Work' or 'iCloud'). | |
| JXA_MAIL_DEFAULT_MAILBOX | No | Set the default Apple Mail mailbox to use for queries (e.g., 'Inbox'). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List all configured email accounts in Apple Mail. Returns: List of account dictionaries with 'name' and 'id' fields. Example: >>> list_accounts() [{"name": "Work", "id": "abc123"}, {"name": "Personal", "id": "def456"}] |
| list_mailboxesA | List all mailboxes for an email account. Args: account: Account name. Uses JXA_MAIL_DEFAULT_ACCOUNT env var or first account if not specified. Returns: List of mailbox dictionaries with 'name' and 'unreadCount' fields. Example: >>> list_mailboxes("Work") [{"name": "INBOX", "unreadCount": 5}, ...] |
| get_emailsA | Get emails from a mailbox. Retrieves emails with standard properties: id, subject, sender, date_received, read status, and flagged status. Args: account: Account name. Uses JXA_MAIL_DEFAULT_ACCOUNT env var or first account if not specified. mailbox: Mailbox name. Uses JXA_MAIL_DEFAULT_MAILBOX env var or "Inbox" if not specified. limit: Maximum number of emails to return (default: 50) Returns: List of email dictionaries sorted by date (newest first). Example: >>> get_emails("Work", "INBOX", limit=10) [{"subject": "Meeting tomorrow", "sender": "boss@work.com", ...}, ...] |
| get_todays_emailsA | Get all emails received today from a mailbox. Args: account: Account name. Uses JXA_MAIL_DEFAULT_ACCOUNT env var or first account if not specified. mailbox: Mailbox name. Uses JXA_MAIL_DEFAULT_MAILBOX env var or "Inbox" if not specified. Returns: List of today's emails sorted by date (newest first). Example: >>> get_todays_emails("Work") [{"subject": "Urgent: Review needed", "sender": "team@work.com", ...}] |
| get_unread_emailsA | Get unread emails from a mailbox. Args: account: Account name. Uses JXA_MAIL_DEFAULT_ACCOUNT env var or first account if not specified. mailbox: Mailbox name. Uses JXA_MAIL_DEFAULT_MAILBOX env var or "Inbox" if not specified. limit: Maximum number of emails to return (default: 50) Returns: List of unread emails sorted by date (newest first). Example: >>> get_unread_emails("Work", limit=20) [{"subject": "New message", "read": false, ...}, ...] |
| get_flagged_emailsA | Get flagged emails from a mailbox. Args: account: Account name. Uses JXA_MAIL_DEFAULT_ACCOUNT env var or first account if not specified. mailbox: Mailbox name. Uses JXA_MAIL_DEFAULT_MAILBOX env var or "Inbox" if not specified. limit: Maximum number of emails to return (default: 50) Returns: List of flagged emails sorted by date (newest first). Example: >>> get_flagged_emails("Work") [{"subject": "Important task", "flagged": true, ...}, ...] |
| search_emailsA | Search for emails matching a query string. Searches in both subject and sender fields (case-insensitive). Args: query: Search term to look for account: Account name. Uses JXA_MAIL_DEFAULT_ACCOUNT env var or first account if not specified. mailbox: Mailbox name. Uses JXA_MAIL_DEFAULT_MAILBOX env var or "Inbox" if not specified. limit: Maximum number of results (default: 50) Returns: List of matching emails sorted by date (newest first). Example: >>> search_emails("invoice", "Work") [{"subject": "Invoice #123", "sender": "billing@vendor.com", ...}] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Multiple tools have overlapping purposes that could cause confusion. get_emails, get_flagged_emails, get_todays_emails, and get_unread_emails all retrieve emails with different filters, but their boundaries are unclear—an agent might struggle to choose between them when multiple criteria apply. The descriptions help somewhat, but the functional overlap is significant.
Tool names follow a consistent verb_noun pattern throughout (e.g., get_emails, list_accounts, search_emails). All tools use snake_case with clear, descriptive names that align with their functions, making the set predictable and easy to understand.
With 7 tools, the count is well-scoped for an email management server. Each tool serves a distinct, useful purpose in the domain (e.g., retrieving emails, listing accounts/mailboxes, searching), and none feel redundant or missing in terms of quantity for the apparent scope.
There are significant gaps in the tool surface for email management. The server lacks essential CRUD operations like creating, sending, updating (e.g., marking as read/unread), or deleting emails, which are core to the domain. This will likely cause agent failures when trying to perform common email tasks beyond retrieval and listing.