Gmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_MCP_TOKEN_PATH | No | Custom path to the token cache file where authentication tokens are stored. | ~/.config/gmail-mcp/token.json |
| GMAIL_MCP_CREDENTIALS_PATH | Yes | Path to your Google Cloud OAuth credentials JSON file. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_unreadB | List unread emails from inbox. Args: max_results: Maximum number of emails to return (1-100). Default: 20. Returns: List of email objects with id, from, subject, date, snippet, labels, body_preview. |
| searchA | Search emails using Gmail query syntax. Args: query: Gmail search query (e.g., "from:user@example.com is:unread", "subject:invoice", "newer_than:1d"). max_results: Maximum number of results (1-100). Default: 20. Returns: List of email objects matching the query. |
| archiveA | Archive emails by removing INBOX and UNREAD labels. Args: message_ids: List of message IDs to archive. Returns: Dict with archived_count, failed_count, and details. |
| mark_as_readA | Mark emails as read without archiving. Args: message_ids: List of message IDs to mark as read. Returns: Dict with marked_count, failed_count, and details. |
| get_labelsB | Get all Gmail labels for the authenticated user. Returns: List of label objects with id, name, type, and message counts. |
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 5 tools
Each tool has a distinct and clear purpose: archive emails, get labels, list unread emails, mark emails as read, and search emails. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., archive, get_labels, list_unread, mark_as_read, search). The naming is straightforward and predictable, enhancing usability and clarity.
With 5 tools, the server is well-scoped for basic Gmail operations, covering key actions like reading, archiving, and searching emails. However, it lacks some advanced features like sending or deleting emails, which slightly limits its completeness but keeps the count reasonable.
The tool set covers essential read and modify operations (list, search, mark as read, archive) and label management, but it has notable gaps: there are no tools for sending emails, deleting emails, or managing drafts. This could lead to agent failures for common email workflows like composing or removing messages.