@openmaxai/email-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAP_HOST | No | IMAP server hostname. | |
| IMAP_PORT | No | IMAP server port (default 993 for SSL, 143 otherwise). | |
| POP3_HOST | No | POP3 server hostname. | |
| POP3_PORT | No | POP3 server port (default 995 for SSL, 110 otherwise). | |
| SMTP_HOST | Yes | SMTP server hostname. | |
| SMTP_PORT | No | SMTP server port (default 465 for SSL, 587 for STARTTLS, 25 for none). | |
| EMAIL_USER | Yes | Login name, usually the full email address. Also used as the From address. | |
| IMAP_SECURE | No | IMAP security mode: 'ssl' (implicit TLS), 'starttls', or 'none'. | |
| POP3_SECURE | No | POP3 security mode: 'ssl' or 'none' (STARTTLS is not supported). | |
| SMTP_SECURE | No | SMTP security mode: 'ssl', 'starttls', or 'none'. | |
| EMAIL_ALIASES | No | Other addresses of this mailbox, comma-separated. | |
| EMAIL_PASSWORD | Yes | App password / authorization code. The only secret. | |
| EMAIL_FROM_NAME | No | Display name for the From header. | |
| EMAIL_LOG_LEVEL | No | Log level for stderr output. | info |
| EMAIL_SAVE_SENT | No | IMAP only: save a copy to the Sent folder after sending. | true |
| EMAIL_TIMEOUT_MS | No | Timeout for each tool call's network work (1000 to 600000). | 30000 |
| EMAIL_TLS_VERIFY | No | Verify server TLS certificates. Set to 'false' only for self-signed certificates. | true |
| RECEIVE_PROTOCOL | No | Protocol for receiving email: 'imap' or 'pop3'. | imap |
| EMAIL_ATTACHMENT_ROOTS | No | Directories that attachments may be read from, separated by ':' (or ';' on Windows). | |
| EMAIL_MAX_ATTACHMENT_MB | No | Size limit for each attachment and total per message. | 25 |
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 |
|---|---|
| send_emailB | Send an email via SMTP from user@example.com. Recipients accept "addr@example.com" or "Name addr@example.com". A copy is saved to the IMAP Sent folder. |
| reply_emailA | Reply to a received message (identified by uid or message_id). Sets In-Reply-To / References so the reply stays in the same thread, and prefixes the subject with "Re:". |
| list_emailsB | List the newest messages in a folder (via IMAP), newest first. Returns summaries: uid, from, to, subject, date, flags/seen, snippet. |
| get_emailA | Read one message by uid. format=full returns text/html bodies; format=headers returns only headers. include_attachments=true saves attachments to a private temp dir and returns their paths. |
| search_emailsC | Search messages (case-insensitive substring match). since/before are dates (YYYY-MM-DD); since is inclusive, before exclusive. Runs server-side via IMAP SEARCH. |
| list_foldersA | List IMAP folders with message / unseen counts. |
| mark_readA | Set or clear the \Seen flag on a message. |
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 7 tools
Each tool targets a distinct email operation: sending, replying, listing, reading, searching, managing folders, and toggling read status. Even though list_emails and search_emails both return messages, their purposes are clearly separated by folder listing vs. substring search.
All tool names consistently follow a verb_noun pattern: send_email, reply_email, list_emails, get_email, search_emails, mark_read, list_folders. This makes the tool set highly predictable and easy for an agent to navigate.
Seven tools is well-scoped for an email MCP server. Each tool covers a meaningful operation without redundancy or bloat.
Core email workflows are well covered: send, reply, list, search, read, mark read, and folder listing. Minor gaps exist around operations like deleting/moving messages or sending attachments, but agents can typically accomplish common email tasks without dead ends.