mailmate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_messages_toolA | Search MailMate messages by query string and/or tag. query and tag are both optional — omit query to list all messages with a given tag, or omit tag to search by text only. Use list_tags to see available tags. Returns a list of matching messages with subject, from, to, date, mailbox, tags, and message_url for each. |
| get_messageA | Get full details of a specific email by its message:// URL. Returns headers, metadata, tags, and optionally the body. |
| list_mailboxesA | List all mailboxes across all configured MailMate accounts. Returns account name, mailbox path, and message count for each. |
| get_message_linkA | Get the message:// link for a message and open it in MailMate. The returned URL can be pasted into any app to jump directly to the message in MailMate (same as Edit > Copy as Link). |
| open_message_in_mailmateA | Open a specific message in MailMate by its message:// URL. Activates MailMate and navigates to the message. |
| move_messageA | Move a message to a different mailbox. MailMate performs the actual IMAP MOVE, so the message will be moved on the server as well. Provide the 'path' from list_mailboxes or just a mailbox name — if a name is given, the first matching mailbox across all accounts is used. |
| tag_messageA | Add or remove tags on a message. Tags are stored as IMAP Keywords headers and synced to the server. MailMate will pick up the change on next access. Use list_tags to see what tags are defined in MailMate. |
| list_tagsA | List all tags defined in MailMate. Tags correspond to IMAP keywords and are configured in MailMate > Preferences > Tags. |
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 8 tools
Most tools target distinct actions, but open_message_in_mailmate and get_message_link both open a message in MailMate, making their purposes fuzzy. get_message, get_message_link, and open_message_in_mailmate also form a confusingly similar group of message-URL tools.
The set mostly follows a verb_noun pattern: list_tags, list_mailboxes, get_message, move_message, tag_message. The main deviations are the awkward search_messages_tool suffix and the longer open_message_in_mailmate form, but the pattern remains predictable.
Eight tools is a well-scoped size for a MailMate server covering search, retrieval, navigation, mailbox listing, tagging, and moving messages. Each tool feels justified even if a couple overlap.
Retrieval and organization workflows are covered: search, read, move, tag, and open. However, an email client surface lacks obvious send/reply/delete and mark-read operations, and the search tool cannot filter by mailbox, which are notable gaps.