Gmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANGO_BASE_URL | No | The base URL for the Nango API. | https://api.nango.dev |
| GMAIL_MCP_DEBUG | No | Enable debug logging by setting this environment variable to true. | |
| GOOGLE_CLIENT_ID | No | Your Google OAuth client ID (Alternative to Nango). | |
| NANGO_SECRET_KEY | No | Your Nango secret key. | |
| NANGO_CONNECTION_ID | No | Your Nango connection ID. | |
| GOOGLE_CLIENT_SECRET | No | Your Google OAuth client secret (Alternative to Nango). | |
| GOOGLE_REFRESH_TOKEN | No | Your Google OAuth refresh token (Alternative to Nango). | |
| NANGO_INTEGRATION_ID | No | Your Nango integration ID (e.g., google or google-mail). |
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 |
|---|---|
| gmail_list_messagesB | List Gmail messages with optional search query. Args: query: Gmail search query (e.g., 'from:sender@example.com', 'is:unread') max_results: Maximum number of messages to return (1-100) Returns: Dictionary with success status and message data |
| gmail_get_messageC | Get details of a specific Gmail message. Args: message_id: Gmail message ID Returns: Dictionary with message details or error |
| gmail_send_messageB | Send a Gmail message. Args: to: Recipient email address subject: Email subject body: Email body content cc: CC recipients (comma-separated) bcc: BCC recipients (comma-separated) Returns: Dictionary with send result |
| gmail_search_messagesB | Search Gmail messages with specific criteria. Args: sender: Filter by sender email subject: Filter by subject keywords after_date: Filter messages after date (YYYY/MM/DD format) before_date: Filter messages before date (YYYY/MM/DD format) has_attachment: Filter messages with attachments is_unread: Filter unread messages max_results: Maximum number of messages to return (1-100) Returns: Dictionary with search results |
| gmail_mark_as_readB | Mark Gmail messages as read. Args: message_ids: List of message IDs to mark as read Returns: Dictionary with operation result |
| gmail_delete_messagesC | Delete Gmail messages. Args: message_ids: List of message IDs to delete Returns: Dictionary with operation result |
| gmail_get_statsC | Get Gmail account statistics. Args: include_unread: Include unread message count Returns: Dictionary with account statistics |
| gmail_send_message_with_attachmentB | Send Gmail message with attachment. Args: to: Recipient email address subject: Email subject body: Email body content file_path: Path to file to attach cc: CC recipients (comma-separated) Returns: Dictionary with send result |
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 8 tools
There is overlap between gmail_list_messages and gmail_search_messages, as both retrieve messages with filtering, though search offers more specific criteria. Similarly, gmail_send_message and gmail_send_message_with_attachment are nearly identical except for the attachment parameter. This could cause agent confusion.
All tool names follow a consistent 'gmail_verb_noun' pattern in snake_case. Every name clearly indicates the action and resource, e.g., gmail_list_messages, gmail_get_message, gmail_send_message.
With 8 tools, the server covers essential Gmail operations without being overwhelming. The count is well-scoped for a focused MCP server, providing a balanced set of capabilities.
The tool set covers core email operations: send, receive, list, search, mark read, delete, and stats. Missing features like label management and draft handling are minor gaps, but the current surface supports primary workflows effectively.