Maily MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| maily_list_accountsA | Lists the email profiles available in Maily (id, email, name, color).
Use the email or the name as the |
| maily_list_messagesB | Lists the recent messages of a profile. |
| maily_get_messageA | Returns the full content of a message (sender, recipients, date,
subject, text body, attachments with their attachment_id). Set
|
| maily_searchB | Local full-text search (subject, body, sender). Optional |
| maily_syncA | Syncs from the mail server (fetches new messages). Without |
| maily_sendA | Sends an email FROM a profile (Gmail accounts only). Irreversible action: ask the user for confirmation before calling this tool. |
| maily_export_emlA | Saves a message as an .eml file (raw RFC 822) on disk. dest_path : folder or full path inside ~/Downloads, ~/Desktop or ~/Documents (default: ~/Downloads). An existing file is never overwritten: a number is added to the name. Works for Gmail and IMAP accounts. Returns the path of the written file. |
| maily_download_attachmentA | Downloads an attachment of a message to disk. dest_path : folder or full path inside ~/Downloads, ~/Desktop or ~/Documents (default: ~/Downloads). An existing file is never overwritten: a number is added to the name. |
| maily_trashA | Moves a message to the trash. Reversible for a Gmail profile; for an IMAP profile the message goes to the server's trash folder and Maily cannot restore it. If the IMAP account has no trash folder, the tool refuses (code "no_trash_folder") and leaves the message untouched. Management action: confirm with the user before calling this tool. |
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 9 tools
Each tool targets a distinct operation: listing, reading, searching, sending, syncing, trashing, exporting, and downloading attachments. The only mild overlap is between maily_export_eml and maily_download_attachment, since both write files to disk, but their descriptions clearly separate whole-message export from single-attachment download.
All names share a consistent maily_ prefix and snake_case, and most follow a verb_noun pattern (list_messages, get_message, download_attachment). A few are bare verbs (search, send, sync, trash), which is a minor deviation but still readable and predictable.
Nine tools is well within the ideal 3-15 range and each one covers a distinct capability of an email client. No tool feels redundant or tacked on.
Core read/send/search/trash/sync/export workflows are covered, but there are notable gaps: no way to mark messages read/unread, no move/archive tool despite list_messages exposing an 'archived' category, and no reply/forward or draft operations. Agents can partially work around these via send, but the lifecycle is asymmetric.