gmail-attachments-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Hosted mode only: bearer token protecting the /mcp endpoint. Must be at least 32 characters or the server rejects every request. Usually set by scripts/vercel-setup.sh. | |
| GMAIL_ATT_CLIENT_ID | No | Hosted mode only: OAuth client ID, used instead of token.json. | |
| GMAIL_ATT_CONFIG_DIR | No | Where the Gmail OAuth credentials/token live (defaults to ~/.config/gmail-attachments-mcp/). | |
| GMAIL_ATT_CLIENT_FILE | No | Path to the OAuth client JSON (credentials.json). | |
| GMAIL_ATT_DOWNLOAD_DIR | No | Default download folder for attachments (defaults to ~/Downloads/gmail-attachments). | |
| GMAIL_ATT_CLIENT_SECRET | No | Hosted mode only: OAuth client secret, used instead of token.json. | |
| GMAIL_ATT_REFRESH_TOKEN | No | Hosted mode only: OAuth refresh token, used instead of token.json. |
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_attachmentsA | List attachments on a Gmail message (name, type, size in bytes). |
| download_attachmentA | Save one attachment to disk and return the file path. |
| read_attachment_textA | Return the text of an attachment without saving it. |
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 3 tools
The three tools have clearly distinct purposes: listing attachments, downloading to disk, and reading text without saving. Descriptions explicitly clarify when to use each, with no overlap.
All tools follow a consistent snake_case verb_noun pattern (list_attachments, download_attachment, read_attachment_text). The slight extra noun in the third tool is still clear and predictable.
Three tools are well-scoped for a focused attachment server, covering the core operations of listing, downloading, and reading. No unnecessary tools, and the count feels just right.
The surface covers listing, downloading, and text reading of attachments, which are the primary retrieval workflows. Minor gaps like batch operations or attachment deletion/upload are not addressed, but likely outside the server's intended scope.