Skip to main content
Glama
shuakami

Mail MCP Tool

by shuakami

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IMAP_HOSTYesIMAP server hostname
IMAP_PASSYesIMAP password or app-specific password
IMAP_PORTYesIMAP server port
IMAP_USERYesIMAP username/email
SMTP_HOSTYesSMTP server hostname
SMTP_PASSYesSMTP password or app-specific password
SMTP_PORTYesSMTP server port
SMTP_USERYesSMTP username/email
IMAP_SECUREYesWhether to use secure connection for IMAP
SMTP_SECUREYesWhether to use secure connection for SMTP
DEFAULT_FROM_NAMEYesDefault sender name
DEFAULT_FROM_EMAILYesDefault 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

NameDescription
sendBulkMailD
sendMailD
sendSimpleMailD
sendHtmlMailD
waitForReplyD
searchEmailsD
listEmailsD
getContactsD
getEmailDetailD
deleteEmailD
moveEmailD
getAttachmentD
listFoldersD
markMultipleAsReadD
markMultipleAsUnreadD
markAsReadD
markAsUnreadD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.8/5.0

Scored across 17 tools

Disambiguation3/5

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.

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues