Gmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_TOKEN_PATH | No | Path to the saved token file. Defaults to <project>/token.json. | |
| GMAIL_CREDENTIALS_PATH | No | Path to the OAuth client file downloaded from Google Cloud. Defaults to <project>/credentials.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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_emailsA | Search the mailbox with Gmail search syntax. Returns id, threadId, from, to, subject, date, snippet and labels for each match, newest first. |
| get_emailA | Read one email: headers, plain-text body (HTML converted to text if there is no plain part) and attachment names and sizes. Attachment contents are never returned. |
| get_threadA | Read every message in a thread, oldest first, each in the same format as get_email. |
| create_draft_replyA | Save a plain-text reply to an email as a Gmail draft, in the same thread, addressed to the original sender (its Reply-To if set). Nothing is sent: a person reviews and sends the draft from Gmail. |
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 4 tools
Each tool has a clearly distinct purpose: search messages, read a single email, read a thread, or create a draft reply. There is no ambiguous overlap; get_email and get_thread differ by message vs. thread scope and descriptions make that clear.
All names use consistent snake_case verb_noun phrasing. The pattern is predictable across search_emails, get_email, get_thread, and create_draft_reply.
Four tools is a reasonable, focused set for a read-and-draft-reply workflow. It is slightly thin for a Gmail server overall, but each included tool earns its place.
The set covers searching, reading, thread reading, and saving draft replies, but omits core Gmail operations such as sending, label management, deletion/trash, and attachment retrieval. These are notable gaps for an agent expecting general Gmail functionality.