Gmail no-CASA MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_OAUTH_BEARER | Yes | A fresh OAuth bearer token for Gmail API access |
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 |
|---|---|
| send_emailA | Send one plain-text email from the connected Gmail account. The host must obtain fresh explicit approval for every call and show the exact to, cc, bcc, subject, and complete body. A response lost after dispatch has an unknown outcome and must never be retried automatically. |
| create_labelA | Create one Gmail user label by exact name. This is an external write; it does not apply the label to messages or threads. |
| update_labelA | Update one Gmail user label resolved by its exact current name. This can rename the label or change its Gmail visibility settings; it does not modify message membership. |
| delete_labelA | Permanently delete one Gmail user label resolved by exact name. Deleting the label removes it from every affected message and thread, so the host must obtain explicit consequence-aware approval. |
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 targets a distinct action: create, delete, update labels, and send email. No overlap between label operations and email sending.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_label, send_email), making them predictable.
With 4 tools, the set is on the lower end but within the typical 3-15 range. More tools could be useful, but the count is not problematic.
The server lacks fundamental Gmail operations such as reading, searching, or listing emails, and label tools do not allow applying labels to messages, leaving significant gaps.