IMAP Email MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMAP_TLS | No | Whether to use TLS for the IMAP connection. | true |
| IMAP_HOST | Yes | The hostname of the IMAP server (e.g., imap.example.com). | |
| IMAP_PORT | No | The port number for the IMAP server. | 993 |
| IMAP_USER | Yes | The email address to connect to the IMAP server (e.g., your-email@example.com). | |
| SMTP_HOST | No | The hostname of the SMTP server. Defaults to IMAP settings if not specified. | |
| SMTP_PORT | No | The port number for the SMTP server. | 465 |
| SMTP_USER | No | The username for the SMTP server. Defaults to IMAP settings if not specified. | |
| SMTP_SECURE | No | Whether to use a secure connection for SMTP. | true |
| IMAP_PASSWORD | Yes | The app-specific password for the email account. | |
| SMTP_PASSWORD | No | The password for the SMTP server. Defaults to IMAP settings if not specified. | |
| IMAP_AUTH_TIMEOUT | No | Authentication timeout in milliseconds. | 10000 |
| IMAP_TLS_REJECT_UNAUTHORIZED | No | Whether to reject unauthorized TLS certificates. | true |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_foldersB | List all email folders/mailboxes in the IMAP account |
| list_emailsB | List emails from a folder with optional filtering |
| get_emailC | Get full email content by UID |
| search_emailsC | Search emails by subject, from, or body text |
| list_draftsC | List all draft emails |
| get_draftC | Get a specific draft email by UID |
| create_draftC | Create a new draft email |
| update_draftC | Update an existing draft by deleting old and creating new |
| send_emailC | Send an email directly |
| delete_emailB | Delete an email by UID |
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 10 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, list_emails retrieves emails from a folder, while search_emails filters by content, and get_email fetches full content of a specific email. The draft-related tools (create_draft, get_draft, list_drafts, update_draft) are well-separated from email management tools, ensuring agents can easily select the right tool for each task.
All tool names follow a consistent verb_noun pattern using snake_case, such as list_folders, create_draft, and send_email. This predictability makes the tool set easy to navigate and understand, with no deviations in naming conventions across the ten tools.
With 10 tools, the server is well-scoped for email management via IMAP. Each tool earns its place by covering essential operations like listing, creating, retrieving, updating, and deleting emails and drafts, without being overly sparse or bloated for the domain.
The tool surface provides strong coverage for core email workflows, including CRUD operations for emails and drafts, folder management, and sending. A minor gap is the lack of tools for moving emails between folders or marking them as read/unread, but agents can work around this with the existing tools for basic email handling.