Assistant Mail
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASSISTANT_MAIL_API_KEY | No | API key (amk_...). Can be omitted if passed per-tool. | |
| ASSISTANT_MAIL_API_BASE_URL | No | The public API for the AssistantMail service. | https://api.assistant-mail.ai |
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 |
|---|---|
| assistantmail_healthA | Returns AssistantMail MCP server and API endpoint metadata. |
| assistantmail_get_meC | Gets account profile and tier metadata for the authenticated account. |
| assistantmail_get_inbound_policyB | Gets inbound email policy settings for the authenticated account. |
| assistantmail_update_inbound_policyC | Updates inbound email policy for the authenticated account. |
| assistantmail_create_mailboxC | Creates a mailbox for the authenticated account. |
| assistantmail_list_mailboxesB | Lists mailboxes accessible to the authenticated account. |
| assistantmail_get_mailboxC | Gets mailbox metadata for a mailbox ID. |
| assistantmail_update_mailboxC | Updates mailbox metadata (currently display name). |
| assistantmail_delete_mailboxA | Deletes a mailbox and all associated messages. |
| assistantmail_list_messagesC | Lists inbound and outbound messages for a mailbox. |
| assistantmail_get_messageA | Gets a specific message for a mailbox, including hydrated text/html bodies when available. |
| assistantmail_send_emailC | Queues an outbound email for a mailbox. |
| assistantmail_reply_messageB | Replies to an existing message in a mailbox thread. |
| assistantmail_delete_messagesC | Deletes messages from a mailbox by IDs or deletes all messages. |
| assistantmail_get_usageC | Gets daily and monthly send quota usage for a mailbox. |
| assistantmail_list_recipientsC | Lists approved/pending recipients for the authenticated account. |
| assistantmail_add_recipientC | Adds a recipient and sends a consent invitation when required. |
| assistantmail_remove_recipientC | Removes a recipient from the allowed recipient list. |
| assistantmail_send_email_referenceC | Provides the AssistantMail REST endpoint and required headers for email send requests. |
| assistantmail_list_messages_referenceC | Provides the AssistantMail REST endpoint for listing messages (inbound and outbound) in a mailbox. |
| assistantmail_get_message_referenceB | Provides the AssistantMail REST endpoint for fetching a single message including its full body content. |
| assistantmail_get_usage_referenceC | Provides the AssistantMail REST endpoint for checking send quota usage for a mailbox. |
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 22 tools
Most tools map to distinct resources, but the four *_reference tools (get_message_reference, list_messages_reference, send_email_reference, get_usage_reference) closely parallel their non-reference counterparts and could be confused. get_me and health also overlap somewhat as account/server metadata lookups.
Tool names consistently use the assistantmail_ prefix with snake_case verb_noun patterns. Minor deviations (health, *_reference suffix) break the pattern slightly but the convention remains predictable.
22 tools is on the higher end and feels somewhat heavy. The core operations are justified, but the four reference-style tools inflate the count and could have been consolidated.
The server covers the main email lifecycle: mailbox CRUD, message listing/retrieval/send/reply/delete, recipient management, usage, and inbound policy. Minor gaps like message read-state updates or attachment handling are absent, but core workflows are covered.