multi-mail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILMCP_MASTER_KEY | No | The vault key derived from this environment variable if set, otherwise generated locally. |
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_accountsA | List local Gmail and Microsoft 365 account aliases available to this MCP server. No secrets are returned. |
| search_mailA | Search one account or all configured accounts. Gmail uses Gmail search syntax. Microsoft 365 uses Graph message search syntax. |
| get_threadA | Fetch a Gmail thread by threadId or a Microsoft 365 conversation by conversationId. Use ids from search_mail results. |
| create_draftA | Create a draft in Gmail or Microsoft 365. This is the preferred write path before sending. |
| send_draftA | Send an existing draft. Requires confirm: "SEND" to reduce accidental sends. |
| send_mailA | Send a new email immediately. Requires confirm: "SEND". Prefer create_draft unless the user explicitly asks to send now. |
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 6 tools
Each tool has a clearly distinct purpose: create_draft for writing, send_mail for immediate send, send_draft for sending existing drafts, get_thread for retrieving threads, search_mail for searching, and list_accounts for configuration. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_draft, search_mail). No deviations in style or convention.
With 6 tools, the set is well-scoped for an email server supporting two providers. It covers the core operations without being too sparse or excessive.
The tool surface covers essential email lifecycle (create, send, search, retrieve threads) and account listing. Minor gaps exist, such as no tool for updating or deleting drafts, but core workflows are supported.