Cloud Mail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAIL_EMAIL | No | Dedicated user login email. | |
| MAIL_TOKEN | No | Raw user JWT; if provided alongside password, can re-login after session expiry. | |
| MAIL_BASE_URL | Yes | Mail application HTTPS origin; accepts a trailing /api. | |
| MAIL_PASSWORD | No | Dedicated user login password. | |
| MAIL_STATE_DIR | No | Root directory for local drafts and send receipts; absolute path recommended for backup. | ~/.local/state/cloud-mail-mcp |
| MAIL_TIMEOUT_MS | No | Single mailbox request timeout, 100–120000 ms. | 15000 |
| MAIL_ENABLE_WRITE | No | Expose send, reply, send draft, and mark-read tools. | false |
| MAIL_ALLOWED_RECIPIENTS | No | Comma-separated full email addresses allowed for sending; empty uses the mailbox role's allowed range. | |
| MAIL_MAX_ATTACHMENT_BYTES | No | Maximum decoded size for a single download or all attachments in one send, up to 5 MiB. | 1048576 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mail_statusA | Get the authenticated mailbox identity, permissions and MCP configuration. |
| list_mailboxesC | List owned mailbox addresses. Pass nextCursor fields for the next page. |
| list_messagesA | List one mailbox folder, newest first. Reading does not mark messages as read. |
| get_messageA | Read one owned message including text and HTML. Does not mark it read. Folder defaults to inbox. |
| search_messagesB | Search owned mailbox pages by substring (case-insensitive). exhausted=false means partial results; continue with nextBeforeId. Body search includes raw HTML. |
| list_attachmentsC | List attachment metadata for an owned message. |
| download_attachmentB | Read an attachment from an owned message as Base64; subject to MAIL_MAX_ATTACHMENT_BYTES. |
| create_draftC | Save a local draft for this user. Drafts persist across MCP restarts and are separate from browser drafts. |
| list_draftsA | List drafts stored locally for the authenticated user. |
| get_draftB | Read a local draft including content and attachment data. |
| update_draftB | Replace a local draft using its current revision to prevent lost edits. |
| delete_draftC | Delete a local draft using its current revision. |
| get_send_statusA | Read the local receipt for an operationKey. accepted means API acceptance; pending requires reconciliation before any retry. |
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 13 tools
Each tool targets a distinct resource and action: list vs get vs search for messages, metadata vs content for attachments, and complete CRUD separation for drafts. Minor overlaps (list_messages/search_messages, list_mailboxes/mail_status) are clearly differentiated by their descriptions.
Almost all tools follow a predictable snake_case verb_noun pattern (list_, get_, create_, update_, delete_, download_). The noun-first 'mail_status' is an outlier and is slightly inconsistent with 'get_send_status', but the overall convention is strong.
13 tools is well within the ideal 3-15 range for a mail server covering mailboxes, messages, attachments, drafts, and status. Each tool appears to earn its place with no obvious redundancy.
The surface lacks any send operation despite offering get_send_status for send receipts, and message management (delete, move, mark read/unread) is entirely absent. Attachment upload and draft sending are also missing, leaving significant gaps for a cloud mail server.