rubit-mcp-mail
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOME | No | Home directory used to locate configur file and secrets. May need to be set explicitly in stripped-down desktop environments (e.g., Claude Desktop). | |
| PATH | No | Executable search path. May need to be set explicitly when the parent process provides no default PATH. | |
| USER | No | Username of the account running the server. May need to be set explicitly in environments that do not inherit it. | |
| XDG_RUNTIME_DIR | No | Per-user runtime directory (e.g., /run/user/1000). Required for D-Bus and Secret Service keyring access. | |
| RUBIT_MCP_MAIL_LOG_FILE | No | Path to a log file (e.g., /tmp/rubit-mail.log). If not set, logs are written to stderr. | |
| DBUS_SESSION_BUS_ADDRESS | No | D-Bus session bus address (e.g., unix:path=/run/user/1000/bus). Required for keyring access in desktop en environments. | |
| RUBIT_MCP_MAIL_LOG_LEVEL | No | Logging verbosity level (e.g., DEBUG, INFO, WARNING). | INFO |
| RUBIT_MCP_MAIL_NO_KEYRING | No | Set to '1' to disable the OS keyring and use the plain-text secrets file (~/.config/rubit-mcp-mail/secrets.json) instead. Must be set in both the shell where 'rubit-mcp-mail auth' is run and in the MCP server environment. | 0 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List configured mail accounts and whether each is authenticated. Call this first if another tool reports an authentication problem. |
| list_foldersA | List the folders in a mailbox with message and unread counts. Each folder has a normalized |
| list_messagesA | Browse messages in a folder, newest first. Returns summaries only (no bodies). Pass a returned |
| search_messagesA | Search a folder. All supplied criteria are combined with AND. Server-side IMAP search, so it works over the whole folder without downloading anything. Results are newest first. |
| read_messageA | Read one message in full: headers, body text, and attachment metadata. HTML-only mail is converted to text. This does NOT mark the message as read. |
| get_attachmentA | Download one attachment into the configured download directory. Returns the path it was saved to. Files are only ever written inside that one directory; the mailbox itself is not modified. |
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 targets a distinct operation: account auth, folder listing, message browsing, searching, reading, and attachment download. list_messages and search_messages are clearly separated as browse-all versus filtered-search, so there is no real ambiguity.
All tool names follow a consistent verb_noun pattern: list_accounts, list_folders, list_messages, search_messages, read_message, get_attachment. The naming style is uniform and predictable.
Six tools is well-scoped for a read-only email access server. Each tool covers a necessary part of the workflow without redundancy or bloat.
The tool set fully covers the apparent purpose of browsing and reading email: account discovery, folder navigation, message listing/search, full message retrieval, and attachment access. Since the descriptions explicitly indicate a read-only mailbox posture, the lack of send/delete/move tools is not a gap.