MultiMail
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MULTIMAIL_API_KEY | Yes | Your MultiMail API key (mm_live_...) | |
| MULTIMAIL_API_URL | No | API base URL. Defaults to https://api.multimail.dev. | https://api.multimail.dev |
| MULTIMAIL_MAILBOX_ID | No | Default mailbox ID. If not set, pass mailbox_id to each tool or call list_mailboxes first. |
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 this API key. Returns each mailbox's ID, email address, oversight mode, and display name. Use this to discover your mailbox ID if MULTIMAIL_MAILBOX_ID is not set. |
| send_emailA | Send an email from your MultiMail address. The body is written in markdown and automatically converted to formatted HTML for delivery. If the mailbox is in read_only mode, this returns a 403 error with upgrade instructions — use request-upgrade to ask the operator for more autonomy. If the mailbox uses gated oversight, the response status will be 'pending_approval' — this means the email is queued for human review. Do not retry or resend when you see pending_approval. |
| check_inboxA | List emails in your inbox. Returns email summaries including id, from, to, subject, status, received_at, and has_attachments. Does NOT include the email body — call read_email with the email ID to get the full message content. |
| read_emailA | Get the full content of a specific email, including the markdown body and attachment metadata. Automatically marks unread emails as read. Use the email ID from check_inbox results. |
| reply_emailA | Reply to an email in its existing thread. Threading headers (In-Reply-To, References) are set automatically. The body is written in markdown. If the mailbox is in read_only mode, this returns a 403 error with upgrade instructions. If the mailbox uses gated oversight, the response status will be 'pending_approval' — the reply is queued for human review. Do not retry or resend when you see pending_approval. |
| search_identityA | Look up the public identity document for any MultiMail email address. Returns the agent's operator, oversight mode, capabilities, and whether the operator is verified. No authentication required. Use this to verify another agent's identity before sending sensitive information. |
| resend_confirmationA | Resend the operator anti-spam confirmation email. Use this if the account is stuck in 'pending_operator_confirmation' status because the original confirmation email was lost or filtered. Rate limited to 1 request per 5 minutes. Only works for unconfirmed accounts. |
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 has a distinct and clearly defined purpose with no overlap. For example, check_inbox lists emails, read_email retrieves full content, send_email and reply_email handle different sending actions, and search_identity serves a unique verification function. The descriptions explicitly differentiate tools, preventing agent misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as check_inbox, list_mailboxes, and send_email. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 7 tools, the server is well-scoped for email management, covering core operations like reading, sending, replying, searching, and administrative tasks. Each tool serves a necessary function without redundancy, fitting the domain appropriately.
The tool set covers essential email workflows including inbox checking, reading, sending, replying, identity verification, and administrative actions. A minor gap exists in lacking explicit tools for deleting emails or managing attachments beyond metadata, but agents can work around this with the provided operations.