Fastmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMAIL_API_TOKEN | Yes | Fastmail API token | |
| FASTMAIL_ACCOUNT_ID | No | Account ID; auto-detected when omitted | |
| FASTMAIL_FOOTER_HTML | No | Optional HTML footer added to sent mail | |
| FASTMAIL_SIGNATURE_NAME | No | Name shown in the optional signature | |
| FASTMAIL_DRAFT_BY_DEFAULT | No | Set to false to send right away instead of saving drafts |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fastmail_get_accountB | Get Fastmail account information and session details. |
| fastmail_list_emailsA | List emails from your inbox or other folders. Supports filtering by folder, read status, and search. |
| fastmail_get_emailA | Get detailed information about a specific email by its ID. |
| fastmail_send_emailA | Compose and send (or save as draft) an email from the account's own Fastmail identity. IMPORTANT — DEFAULT TO DRAFT: unless the context clearly implies the email should go out immediately (explicit instruction, routine automated alert, or an established-contact follow-up), save it as a draft so a human can review before it sends. Omit saveDraft to use the configured default (draft-first unless FASTMAIL_DRAFT_BY_DEFAULT=false). Send as the account owner. Never add AI/agent signatures or self-identification; any machine-authorship marker is configured server-side via FASTMAIL_FOOTER_HTML. |
| fastmail_list_masked_emailsB | List all masked email addresses (privacy-focused aliases). |
| fastmail_create_masked_emailB | Create a new masked email address for privacy protection. |
| fastmail_update_masked_emailA | Update a masked email (enable, disable, or change description). |
| fastmail_delete_masked_emailB | Delete a masked email address. |
| fastmail_mark_email_readA | Mark an email as read or unread. |
| fastmail_mark_email_flaggedA | Flag or unflag an email (star). |
| fastmail_list_foldersA | List all email folders. |
| fastmail_get_unread_countA | Get unread email count for inbox or a specific folder. |
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 12 tools
Each tool targets a distinct resource and action: account info, email listing/detail/sending, masked email CRUD, read/flag state, folders, and unread count. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tool names follow a consistent snake_case pattern with the fastmail_ prefix and verb_noun structure (get, list, send, create, update, delete, mark). The naming is predictable and makes the toolset easy to navigate.
With 12 tools, the server is well-scoped for its domain: email operations, masked email management, folders, and account info. Each tool has a clear purpose, and the count is neither bloated nor too thin.
Masked emails have full CRUD coverage and core email reading/sending/flagging is supported. However, notable gaps exist in the email lifecycle: there is no delete, move/archive, or folder mutation capability, so agents cannot perform common cleanup or organization workflows.