Gmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOW_GMAIL_SEND | No | Enable Gmail send. Set to 'true' to allow. | false |
| ALLOW_GMAIL_DRAFT_CREATE | No | Enable Gmail draft creation. Set to 'true' to allow. | false |
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 |
|---|---|
| health_checkA | Verify that the MCP server is running and show integration status. |
| echo_textA | Echo non-empty text to verify argument handling and tool responses. |
| add_numbersA | Add two numbers to verify typed numeric tool arguments. |
| gmail_auth_statusA | Check local Gmail OAuth credential and token readiness without a network call. |
| gmail_get_profileA | Verify the Gmail API connection and return mailbox totals. |
| gmail_list_messagesC | List recent Gmail messages with IDs, sender, subject, date, and snippet. |
| gmail_search_messagesB | Search Gmail using Gmail search syntax such as from:, subject:, or is:unread. |
| gmail_read_messageA | Read a Gmail message using a message_id returned by list or search. |
| gmail_create_draftC | Create a Gmail draft after explicit enablement in .env. |
| gmail_send_emailC | Send an email after explicit enablement in .env. |
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 10 tools
Gmail-specific tools have distinct purposes, but the inclusion of add_numbers and echo_text creates a confusing mix of unrelated functionalities, potentially causing an agent to select the wrong tool.
Most Gmail tools follow a gmail_verb_noun pattern, but health_check, add_numbers, and echo_text break this convention, leading to inconsistent naming.
With 10 tools, the count is reasonable for a Gmail integration, but the presence of two test tools inflates the count unnecessarily and feels out of place.
The tool surface lacks essential operations like deleting messages, managing labels, or updating drafts, leaving significant gaps for a comprehensive email workflow.