Mail MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAP_HOST | Yes | IMAP server hostname | |
| IMAP_PASS | Yes | IMAP password or app-specific password | |
| IMAP_PORT | Yes | IMAP server port | |
| IMAP_USER | Yes | IMAP username/email | |
| SMTP_HOST | Yes | SMTP server hostname | |
| SMTP_PASS | Yes | SMTP password or app-specific password | |
| SMTP_PORT | Yes | SMTP server port | |
| SMTP_USER | Yes | SMTP username/email | |
| IMAP_SECURE | Yes | Whether to use secure connection for IMAP | |
| SMTP_SECURE | Yes | Whether to use secure connection for SMTP | |
| DEFAULT_FROM_NAME | Yes | Default sender name | |
| DEFAULT_FROM_EMAIL | Yes | Default sender email address |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
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 17 tools
Most tools have distinct purposes targeting different email operations, but there's some overlap between sendMail, sendSimpleMail, sendHtmlMail, and sendBulkMail that could cause confusion about which to use for basic sending. The marking tools (markAsRead/markAsUnread vs markMultipleAsRead/markMultipleAsUnread) are clearly differentiated by single vs batch operations.
The naming follows a consistent verb-first pattern with camelCase throughout (e.g., deleteEmail, getAttachment, listEmails). Minor deviation exists with 'waitForReply' which uses a different verb style, but overall the convention is predictable and readable.
With 17 tools, the count is slightly high but reasonable for an email management server covering folders, emails, contacts, attachments, and sending operations. It's comprehensive without being overwhelmingly bloated, though some consolidation might improve efficiency.
The toolset covers core email workflows well, including listing, reading, sending, searching, organizing (move/delete), and status management (mark read/unread). Minor gaps include no update/delete for contacts or folders, and no tool for managing email drafts, but agents can work around these with the provided operations.