Gmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_PASS | Yes | Gmail App Password (not your regular password) | |
| GMAIL_USER | Yes | Your Gmail address |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailB | Send an email using Gmail SMTP |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'send_email' has a clear and distinct purpose that cannot be mistaken for any other tool in this set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'send_email' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A Gmail server with only one tool is too limited for its apparent scope. Gmail involves operations like reading, listing, deleting, and managing emails, so a single send tool leaves significant functionality uncovered, making it inappropriate for comprehensive use.
The tool set is severely incomplete for a Gmail server. It only supports sending emails, missing essential operations such as retrieving, listing, deleting, or managing emails and labels. This gap will cause frequent agent failures when trying to perform common Gmail tasks.