MCP server for AssistantMail — give AI agents a managed mailbox to send and receive email.
assistantmail-mcp is an MCP project maintained in the assistantmail/assistantmail-mcp repository. The maintainer describes its purpose as “MCP server for AssistantMail — give AI agents a managed mailbox to send and receive email”. Read the project documentation for the complete scope.
The documented npm package is @assistantmail/assistantmail-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares ASSISTANT_MAIL_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| assistantmail_health | Check that the MCP server is running and confirm the API base URL. No API key required. |
| assistantmail_get_me | Get account profile and plan tier. |
| assistantmail_get_inbound_policy | Get the current inbound email policy (who can send to this account's mailboxes). |
| assistantmail_update_inbound_policy | Update the inbound policy (if allowed by selected account tier). Accepted values: owner, list, sent. Use allowedSenders with list. |
| assistantmail_list_mailboxes | List all mailboxes on the account. Returns mailboxId needed for message operations. |
| assistantmail_create_mailbox | Create a new mailbox (if allowed by selected account tier), optionally specifying displayName and address. |
| assistantmail_get_mailbox | Get metadata for a single mailbox by mailboxId. |
| assistantmail_update_mailbox | Update a mailbox's display name. |
| assistantmail_delete_mailbox | Permanently delete a mailbox and all its messages. THIS ACTION HAS NO CONFIRMATION. USE CAREFULLY. |
| assistantmail_list_messages | List inbound and outbound messages for a mailbox. Supports since (ISO timestamp) and limit (max 100). |
| assistantmail_get_message | Fetch a single message including textBody and htmlBody. Bodies are only returned within the plan's retention window; bodyExpired: true is set if the window has |
| assistantmail_send_email | Queue an outbound email. Requires to, subject, and at least one of text or html. |
| assistantmail_reply_message | Reply to an existing message. Requires messageId and at least one of text or html; recipients and subject are derived automatically. |
| assistantmail_delete_messages | Delete messages by messageIds array, or pass deleteAll: true to clear the mailbox. |
| assistantmail_get_usage | Get daily and monthly send quota usage for a mailbox. A null limit means unlimited. |
| assistantmail_list_recipients | List approved and pending recipients for the account. |
| assistantmail_add_recipient | Add a recipient. Sends a consent invitation email when required by the account's plan. |
| assistantmail_remove_recipient | Remove a recipient from the allowed list. |
| assistantmail_send_email_reference | Endpoint, headers, and body fields for POST /v1/mailboxes/{mailboxId}/messages. |
| assistantmail_list_messages_reference | Endpoint and query params for GET /v1/mailboxes/{mailboxId}/messages. |
| assistantmail_get_message_reference | Endpoint and response schema for GET /v1/mailboxes/{mailboxId}/messages/{messageId}. |
| assistantmail_get_usage_reference | Endpoint and response schema for GET /v1/mailboxes/{mailboxId}/usage. |
{
"mcpServers": {
"assistantmail": {
"command": "npx",
"args": [
"-y",
"@assistantmail/assistantmail-mcp"
],
"env": {
"ASSISTANT_MAIL_API_KEY": "YOUR_ASSISTANT_MAIL_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| ASSISTANT_MAIL_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.