claude-gmail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_ADDRESS | No | Your Gmail address (required for SMTP/IMAP backend) | |
| GMAIL_TOKEN_PATH | No | Path to the Gmail OAuth token file (default: ~/.config/claude-gmail-mcp/token.json) | |
| GMAIL_APP_PASSWORD | No | Your Gmail app password (required for SMTP/IMAP backend) |
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 |
|---|---|
| send_emailA | Send an email via Gmail. Args: to: Recipient email address(es). subject: Email subject line. body: Email body content (plain text or HTML). cc: CC recipient(s), optional. bcc: BCC recipient(s), optional. html: If True, send body as HTML instead of plain text. attachments: List of local file paths to attach, optional. Files that cannot be read are skipped with a warning. |
| search_emailsA | Search Gmail using full Gmail search syntax (from:, subject:, is:unread, etc). Pass a single query string for a flat list of results, or a list of queries to run several searches in one call (output is sectioned by query, and max_results applies per query). Returns UID, sender, subject, date, and a Gmail web URL for each match. Args: queries: Single query string or list of query strings. max_results: Max emails to return per query (default 10). |
| read_emailA | Fetch the full content of an email by its UID (from search_emails results). Args: uid: Email UID shown in search_emails output |
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
Each tool has a clearly distinct purpose: reading, searching, and sending emails. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tools follow a consistent verb_noun pattern (read_email, search_emails, send_email), ensuring predictability and ease of use.
With only 3 tools, the set is minimal but covers the core email operations. While slightly under-scoped, it is still reasonable for a focused MCP server.
The tools cover essential read, search, and send operations, but lack common Gmail features like deleting, labeling, or managing drafts, which are notable gaps for a full email client.