Gmail AutoAuth MCP Server

An MCP server for integrating Gmail with auto-authentication support.

A Model Context Protocol (MCP) server for Gmail integration in Claude Desktop with auto authentication support. This server enables AI assistants to manage Gmail through natural language interactions.

- Send emails with subject, content,attachments, and recipients
- Full attachment support- send and receive file attachments
- Download email attachmentsto local filesystem
- Support for HTML emails and multipart messages with both HTML and plain text versions
- Full support for international characters in subject lines and email content
- Read email messages by ID with advanced MIME structure handling
- Enhanced attachment displayshowing filenames, types, sizes, and download IDs
- Search emails with various criteria (subject, sender, date range)
- Comprehensive label management with ability to create, update, delete and list labels
- List all available Gmail labels (system and user-defined)
- List emails in inbox, sent, or custom labels
- Mark emails as read/unread
- Move emails to different labels/folders
- Delete emails
- Batch operations for efficiently processing multiple emails at once
- Full integration with Gmail API
- Simple OAuth2 authentication flow with auto browser launch
- Support for both Desktop and Web application credentials
- Global credential storage for convenience

To install Gmail AutoAuth for Claude Desktop automatically viaSmithery:

npx -y @smithery/cli install @gongrzhe/server-gmail-autoauth-mcp --client claude

- Go toGoogle Cloud Console
- Create a new project or select an existing one
- Enable the Gmail API for your project

# First time: Place gcp-oauth.keys.json in your home directory's .gmail-mcp folder mkdir -p ~/.gmail-mcp mv gcp-oauth.keys.json ~/.gmail-mcp/ # Run authentication from anywhere npx @gongrzhe/server-gmail-autoauth-mcp auth

# Place gcp-oauth.keys.json in your current directory # The file will be automatically copied to global config npx @gongrzhe/server-gmail-autoauth-mcp auth

{ "mcpServers": { "gmail": { "command": "npx", "args": [ "@gongrzhe/server-gmail-autoauth-mcp" ] } } }

docker run -i --rm \ --mount type=bind,source=/path/to/gcp-oauth.keys.json,target=/gcp-oauth.keys.json \ -v mcp-gmail:/gmail-server \ -e GMAIL_OAUTH_PATH=/gcp-oauth.keys.json \ -e "GMAIL_CREDENTIALS_PATH=/gmail-server/credentials.json" \ -p 3000:3000 \ mcp/gmail auth

{ "mcpServers": { "gmail": { "command": "docker", "args": [ "run", "-i", "--rm", "-v", "mcp-gmail:/gmail-server", "-e", "GMAIL_CREDENTIALS_PATH=/gmail-server/credentials.json", "mcp/gmail" ] } } }

For cloud server environments (like n8n), you can specify a custom callback URL during authentication:

npx @gongrzhe/server-gmail-autoauth-mcp auth https://gmail.gongrzhe.com/oauth2callback

Setup Instructions for Cloud Environment

- Set up your n8n container to expose a port for authentication
- Configure a reverse proxy to forward traffic from your domain (e.g.,gmail.gongrzhe.com) to this port

- Add an A record in your DNS settings to resolve your domain to your cloud server's IP address

- In your Google Cloud Console, add your custom domain callback URL (e.g.,https://gmail.gongrzhe.com/oauth2callback) to the authorized redirect URIs list

npx @gongrzhe/server-gmail-autoauth-mcp auth https://gmail.gongrzhe.com/oauth2callback

{ "mcpServers": { "gmail": { "command": "npx", "args": [ "@gongrzhe/server-gmail-autoauth-mcp" ] } } }

This approach allows authentication flows to work properly in environments where localhost isn't accessible, such as containerized applications or cloud servers.

The server provides the following tools that can be used through Claude Desktop:

Sends a new email immediately. Supports plain text, HTML, or multipart emailswith optional file attachments.

{ "to": ["recipient@example.com"], "subject": "Meeting Tomorrow", "body": "Hi,\n\nJust a reminder about our meeting tomorrow at 10 AM.\n\nBest regards", "cc": ["cc@example.com"], "bcc": ["bcc@example.com"], "mimeType": "text/plain" }

{ "to": ["recipient@example.com"], "subject": "Project Files", "body": "Hi,\n\nPlease find the project files attached.\n\nBest regards", "attachments": [ "/path/to/document.pdf", "/path/to/spreadsheet.xlsx", "/path/to/presentation.pptx" ] }

{ "to": ["recipient@example.com"], "subject": "Meeting Tomorrow", "mimeType": "text/html", "body": "<html><body><h1>Meeting Reminder</h1><p>Just a reminder about our <b>meeting tomorrow</b> at 10 AM.</p><p>Best regards</p></body></html>" }

Multipart Email Example (HTML + Plain Text):

{ "to": ["recipient@example.com"], "subject": "Meeting Tomorrow", "mimeType": "multipart/alternative", "body": "Hi,\n\nJust a reminder about our meeting tomorrow at 10 AM.\n\nBest regards", "htmlBody": "<html><body><h1>Meeting Reminder</h1><p>Just a reminder about our <b>meeting tomorrow</b> at 10 AM.</p><p>Best regards</p></body></html>" }

Creates a draft email without sending it.Also supports attachments.

{ "to": ["recipient@example.com"], "subject": "Draft Report", "body": "Here's the draft report for your review.", "cc": ["manager@example.com"], "attachments": ["/path/to/draft_report.docx"] }

Retrieves the content of a specific email by its ID.Now shows enhanced attachment information.

{ "messageId": "182ab45cd67ef" }

Enhanced Response includes attachment details:

Subject: Project Files From: sender@example.com To: recipient@example.com Date: Thu, 19 Jun 2025 10:30:00 -0400 Email body content here... Attachments (2): - document.pdf (application/pdf, 245 KB, ID: ANGjdJ9fkTs-i3GCQo5o97f_itG...) - spreadsheet.xlsx (application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, 89 KB, ID: BWHkeL8gkUt-j4HDRp6o98g_juI...)

4.Download Attachment (download_attachment)

NEW: Downloads email attachments to your local filesystem.

{ "messageId": "182ab45cd67ef", "attachmentId": "ANGjdJ9fkTs-i3GCQo5o97f_itG...", "savePath": "/path/to/downloads", "filename": "downloaded_document.pdf" }

- messageId: The ID of the email containing the attachment
- attachmentId: The attachment ID (shown in enhanced email display)
- savePath: Directory to save the file (optional, defaults to current directory)
- filename: Custom filename (optional, uses original filename if not provided)

Searches for emails using Gmail search syntax.

{ "query": "from:sender@example.com after:2024/01/01 has:attachment", "maxResults": 10 }

Adds or removes labels from emails (move to different folders, archive, etc.).

{ "messageId": "182ab45cd67ef", "addLabelIds": ["IMPORTANT"], "removeLabelIds": ["INBOX"] }

{ "messageId": "182ab45cd67ef" }

8. List Email Labels (list_email_labels)

{ "name": "Important Projects", "messageListVisibility": "show", "labelListVisibility": "labelShow" }

{ "id": "Label_1234567890", "name": "Urgent Projects", "messageListVisibility": "show", "labelListVisibility": "labelShow" }

{ "id": "Label_1234567890" }

12. Get or Create Label (get_or_create_label)

Gets an existing label by name or creates it if it doesn't exist.

{ "name": "Project XYZ", "messageListVisibility": "show", "labelListVisibility": "labelShow" }

13. Batch Modify Emails (batch_modify_emails)

Modifies labels for multiple emails in efficient batches.

{ "messageIds": ["182ab45cd67ef", "182ab45cd67eg", "182ab45cd67eh"], "addLabelIds": ["IMPORTANT"], "removeLabelIds": ["INBOX"], "batchSize": 50 }

14. Batch Delete Emails (batch_delete_emails)

Permanently deletes multiple emails in efficient batches.

{ "messageIds": ["182ab45cd67ef", "182ab45cd67eg", "182ab45cd67eh"], "batchSize": 50 }

Creates a new Gmail filter with custom criteria and actions.

{ "criteria": { "from": "newsletter@company.com", "hasAttachment": false }, "action": { "addLabelIds": ["Label_Newsletter"], "removeLabelIds": ["INBOX"] } }

Gets details of a specific Gmail filter.

{ "filterId": "ANe1Bmj1234567890" }

{ "filterId": "ANe1Bmj1234567890" }

18. Create Filter from Template (create_filter_from_template)

Creates a filter using pre-defined templates for common scenarios.

{ "template": "fromSender", "parameters": { "senderEmail": "notifications@github.com", "labelIds": ["Label_GitHub"], "archive": true } }

You can create filters based on various criteria:

Filters can perform the following actions:

The server includes pre-built templates for common filtering scenarios:

Filters emails from a specific sender and optionally archives them.

{ "template": "fromSender", "parameters": { "senderEmail": "newsletter@company.com", "labelIds": ["Label_Newsletter"], "archive": true } }

2. Subject Filter Template (withSubject)

Filters emails with specific subject text and optionally marks as read.

{ "template": "withSubject", "parameters": { "subjectText": "[URGENT]", "labelIds": ["Label_Urgent"], "markAsRead": false } }

3. Attachment Filter Template (withAttachments)

{ "template": "withAttachments", "parameters": { "labelIds": ["Label_Attachments"] } }

Filters emails larger than a specified size.

{ "template": "largeEmails", "parameters": { "sizeInBytes": 10485760, "labelIds": ["Label_Large"] } }