Mail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port for SSE transport (default: 3000) | |
| IMAP_TLS | No | Use TLS for IMAP (default: true) | |
| SSE_PATH | No | SSE endpoint path (default: /sse) | |
| IMAP_HOST | No | IMAP server hostname (defaults to SMTP_HOST) | |
| IMAP_PASS | No | IMAP password (defaults to SMTP_PASS) | |
| IMAP_PORT | No | IMAP server port (default: 993) | |
| IMAP_USER | No | IMAP username (defaults to SMTP_USER) | |
| SMTP_FROM | No | Default sender email address | |
| SMTP_HOST | Yes | SMTP server hostname | |
| SMTP_PASS | Yes | SMTP password | |
| SMTP_PORT | Yes | SMTP server port (587 or 465) | |
| SMTP_USER | Yes | SMTP username | |
| TRANSPORT | No | Enable SSE transport (set to 'sse') | |
| SMTP_SECURE | No | Use TLS for SMTP (true for port 465, false for STARTTLS on 587) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailA | Send an email via SMTP. Supports HTML and plain text content, attachments, and CC/BCC recipients. |
| verify_connectionB | Verify the SMTP connection and authentication using configured credentials. |
| test_smtp_configA | Test SMTP configuration with custom credentials without modifying the server configuration. |
| get_smtp_infoB | Get information about the current SMTP configuration (without revealing credentials). |
| list_mailboxesA | List all available mailboxes/folders in the IMAP account. |
| fetch_emailsC | Fetch emails from a specific mailbox. Returns email metadata and content. |
| search_emailsB | Search for emails in a mailbox using a search query (searches in subject, from, and body). |
| mark_emailB | Mark an email with a specific flag (read/unread/flagged/unflagged). |
| create_mailboxB | Create a new mailbox/folder in the IMAP account. |
| delete_mailboxB | Delete a mailbox/folder from the IMAP account. |
| move_messageB | Move an email from one mailbox to another. |
| copy_messageA | Copy an email from one mailbox to another. |
| advanced_searchB | Advanced email search with multiple criteria (from, to, subject, body, date range, size, flags). |
| save_draftC | Save an email as a draft in the Drafts folder. |
| get_threadA | Get all emails in a conversation thread based on a message ID. Returns emails sorted chronologically. |
| download_attachmentA | Download a specific attachment from an email. Returns base64-encoded content. |
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 16 tools
Several tools have overlapping purposes: `search_emails` and `advanced_search` both search, with `advanced_search` being a superset; `test_smtp_config` and `verify_connection` both verify SMTP connectivity; `fetch_emails` and `search_emails` have unclear boundaries. The descriptions help but do not fully resolve the ambiguity.
Tool names consistently follow a `verb_noun` pattern with underscores (e.g., `send_email`, `list_mailboxes`, `move_message`). Even multi-word actions like `test_smtp_config` and `get_smtp_info` maintain the pattern. Naming is uniform and predictable.
With 16 tools, the server is slightly above the ideal 3-15 range but still feels scoped to email functionality. Each tool addresses a distinct operation, though some could be consolidated (e.g., search tools, connection verification).
The server covers sending, retrieving, searching, mailbox management, attachments, and drafts. Notable gaps include no direct email deletion operation (though moving to trash is possible) and no explicit update draft operation. These are minor and mostly workaroundable.