uth-mail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UTHMAIL_NAME | No | The display name to use in the From field of your messages. | |
| UTHMAIL_ADDRESS | No | Your full email address if it is not username@uth.gr. | |
| UTHMAIL_PASSWORD | No | Your UTH mail password. Can be used instead of storing credentials in the system keychain. | |
| UTHMAIL_USERNAME | No | Your UTH mail username without @uth.gr. Can be used instead of storing credentials in the system keychain. | |
| UTHMAIL_IMAP_HOST | No | The IMAP host for your department, for example mail.ece.uth.gr. | mail.ds.uth.gr |
| UTHMAIL_DOWNLOAD_DIR | No | Directory where downloaded attachments are saved. | ~/Downloads/uth-mail |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Access to a University of Thessaly email account over IMAP and SMTP: search and read messages, download attachments, mark and move messages, write drafts and send them.
Messages are addressed by folder and uid; uids come from search_messages. Folders can be named as list_folders shows them or as inbox, sent, drafts, trash, junk. Dates are returned as written in the message and normalized in *_iso fields (local time, YYYY-MM-DD HH:MM).
Sending takes two steps: create_draft saves the message in Drafts and send_draft sends it. Only call send_draft after the user has seen that draft and clearly asked for it to be sent.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Check that the login works and see which account, servers and mailbox quota are in use. |
| list_foldersA | All mail folders with their message and unread counts. |
| search_messagesA | Find messages, newest first; with no filters, the latest ones.
|
| get_messageB | A whole message: headers, the text (HTML mail converted to plain text) and its attachments. Reading it does not mark it as read. |
| download_attachmentA | Save one attachment of a message; |
| mark_messagesB | Mark messages as read or unread ( |
| move_messagesA | Move messages to another folder. Moving to trash is how to delete them; they can be moved back from there. |
| create_draftA | Write a message and save it in Drafts. Nothing is sent. To reply, give |
| send_draftA | Send a draft from the Drafts folder and file a copy in Sent. This really sends email: call it only after showing the user that draft (recipients, subject and text) and getting a clear yes for it. |
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 maps to a distinct resource/action: listing folders, searching, fetching a message, downloading an attachment, toggling flags, moving, drafting, sending, and identity check. The only near-pair, create_draft vs send_draft, is explicitly separated by 'nothing is sent' versus the strong 'this really sends email' warning. Reply behavior is folded into create_draft rather than a competing tool, avoiding overlap.
Eight of nine tools follow a clean verb_noun snake_case pattern (list_folders, search_messages, get_message, download_attachment, mark_messages, move_messages, create_draft, send_draft). whoami is the single deviation, though it is a well-understood convention rather than an inconsistency in style.
Nine tools is well within the ideal 3-15 range and every tool earns its place: no redundant variants, no thin wrappers. The surface is scoped tightly to one mailbox workflow without padding.
Core lifecycle is covered: discover folders, search, read, fetch attachments, flag, move/delete via trash, compose drafts (including reply/reply-all), and send. Minor gaps remain, such as forwarding a message, permanently emptying trash, and folder management, but agents can work around these within the stated purpose.