aydu-mail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AYDU_MAIL_HOST | No | IMAP host. | imap.secureserver.net |
| AYDU_MAIL_PASS | Yes | Mailbox password or app password. May alternatively be supplied by the bundled launcher from the OS keyring. | |
| AYDU_MAIL_PORT | No | IMAP port. | 993 |
| AYDU_MAIL_USER | Yes | Full mailbox address; used as IMAP/SMTP user and as the From address. | |
| AYDU_SMTP_HOST | No | SMTP host. | smtpout.secureserver.net |
| AYDU_SMTP_PORT | No | SMTP port. | 465 |
| AYDU_MAIL_SECURE | No | Set false for plaintext/STARTTLS. | true |
| AYDU_SMTP_SECURE | No | Set false on port 587 to require STARTTLS. | true |
| AYDU_MAIL_ALLOW_SEND | No | Set truthy (true, 1, yes, on) to register the send_email tool. Off by default. | false |
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 |
|---|---|
| save_draftA | Save an email as a draft in the account's Drafts folder. It does not send: a human reviews and sends it. Provide both an HTML body and a plain-text alternative. |
| check_connectionA | Verify IMAP connectivity and report which mailbox would receive drafts. Sends nothing. |
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 2 tools
The two tools serve entirely different purposes: one writes a draft, the other checks IMAP connectivity. There is no plausible way to confuse them, and the descriptions reinforce the boundary.
Both names follow a consistent snake_case verb_noun pattern (save_draft, check_connection). No mixing of conventions.
Two tools is on the thin side for a mail server; the surface is narrowly scoped to drafting. It works for the stated purpose but feels sparse.
The stated domain is draft handling, yet there is no way to list, retrieve, update, or delete drafts, only to save and verify connectivity. Notable gaps exist even within the narrow scope.