The reporting tools all work over a trailing number of days rather than an arbitrary date range, and generate_email_analytics will read message bodies when includeContent is set, up to the maxEmails ceiling it is given. On the mailbox side the destructive call is unambiguous: delete_email removes a message permanently, where move_email is the reversible option. Reading and filing address messages and folders by id, so list_mailboxes and list_emails come first in most sequences.
A Fastmail server covering the mailbox itself and a reporting layer over it, from a single account's credentials.
- Browse the account: list_mailboxes for the folder tree, list_emails filtered by mailbox, sender, subject, unread state or free text, get_email for one message in full.
- Find a message by its text with search_emails.
- Send with a text or HTML body, cc and bcc, and an inReplyTo reference when the message answers a thread.
- Act on what you found: mark_email_read, move_email to another folder, delete_email.
- Report over a window of days: get_email_volume_stats for sent and received counts, get_top_senders with counts and percentages, get_activity_patterns by hour, day and month, and generate_email_analytics or generate_email_report for the written version.
A Fastmail account, with FASTMAIL_API_TOKEN in the environment.
One command plus a key — npx -y @alexdiazdecerio/fastmail-mcp-server, then supply credentials