imail-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_mailboxesA | List all mailboxes/folders with their IMAP paths and roles. |
| search_messagesA | Search a mailbox. All filters are optional and combined with AND. Returns summaries, newest first. |
| get_messageA | Fetch a full message: headers, text + HTML body, and attachment metadata. |
| get_threadB | Fetch the conversation a message belongs to, ordered oldest to newest. |
| download_attachmentA | Save an attachment to a local temp file and return its path. Get the attachmentId from get_message. |
| compose_previewA | Build an email and return it for the user to review. Does not send or save anything. Use this first, then send_email after the user approves. |
| send_emailB | Send an email NOW. Only call after the user has explicitly approved sending (ideally after a compose_preview). |
| save_draftA | Save an email to the Drafts mailbox so the user can review and send it themselves. Does not send. |
| replyA | Reply to an existing message. Set replyAll for reply-all. Like send_email, only call after explicit user approval. Threading headers are set automatically from the original. |
| forwardB | Forward an existing message to new recipients. Only call after explicit user approval. |
| move_messageC | Move a message to another mailbox. |
| set_flagsB | Mark a message read/unread and/or flagged/unflagged. |
| archive_messageC | Move a message to the Archive mailbox. |
| delete_messageC | Move a message to Trash (or expunge it if it is already in Trash). |
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 14 tools
Each tool targets a distinct email operation (e.g., archive vs delete vs move, compose vs send vs save draft, forward vs reply). No two tools have overlapping purposes.
Most tools follow verb_noun pattern (e.g., archive_message, delete_message). 'forward' and 'reply' are just verbs, which is a minor inconsistency but still clear.
14 tools cover essential email operations (send, receive, manage folders, flags, attachments, threads) without being excessive.
Covers major email lifecycle (send, receive, delete, move, flag, search, thread). Minor gaps: no direct edit draft or empty trash, but key workflows are supported.