EngageLab Agent Email MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGAGELAB_EMAIL_BASE_URL | No | Override the API base URL. Inferred from the key region: sg → Singapore, tr → Türkiye | |
| ENGAGELAB_EMAIL_SECRET_KEY | Yes | Secret Key starting with sk_ |
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 |
|---|---|
| list_mailboxesA | List all mailboxes available to the authenticated account. Each mailbox has its own address for sending and receiving email. Call this first to discover mailbox IDs used by other tools. |
| send_emailA | Send a new email from one of your EngageLab mailboxes. Provide either text or html body. Recipients are arrays of email addresses. Use sandbox=true for testing without real delivery. |
| list_inbound_messagesB | List inbound (received) email messages, newest first. Optionally filter by mailbox and keyword. |
| get_messageA | Get full details of one inbound message by its UID, including body and attachments. |
| check_new_messagesA | Poll for new inbound messages received since the last check (one-shot; does not block). Use this to monitor an inbox for new email. |
| list_threadsC | List conversation threads. A thread groups messages exchanged with the same counterpart. |
| get_threadB | Get details of one conversation thread. |
| list_thread_messagesA | List all messages inside a conversation thread, oldest first. |
| reply_emailA | Reply to an inbound message. Recipients are inferred from the original message; additional cc/bcc can be added. Provide either text or html body. |
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: mailbox discovery, message listing/retrieval, sending/reply, and thread navigation. The only mild overlap is between check_new_messages and list_inbound_messages, but their descriptions clearly separate the polling behavior from general listing.
All tool names consistently follow the snake_case verb_noun pattern (get_message, list_mailboxes, send_email, reply_email, etc.), with no mixed conventions or vague verbs.
Nine tools is well within the ideal range for an email-focused server, covering mailbox discovery, message operations, sending, replying, and threads without unnecessary bloat.
The core email lifecycle is covered: discover mailboxes, list/read inbound messages, send new emails, reply to existing ones, and inspect threads. Minor gaps include no way to list sent messages and no support for sending attachments, but these are not fatal for typical agent email workflows.