MCP Gmail Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | Yes | The path to the 'src' directory of the mcp-server-gmail project, required for the python module to be discovered. |
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 |
|---|---|
| get_unread_emailsA | Get a list of unread emails |
| create_draft_replyC | Create a draft reply to an email |
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 2 tools
The two tools have clearly distinct purposes: one retrieves unread emails, the other creates draft replies. No overlap or ambiguity.
Both tools follow the verb_noun pattern with snake_case, consistent and predictable naming.
With only 2 tools for a Gmail server, the surface is too thin. A typical Gmail integration would require many more operations.
The tool set is severely incomplete for email management: missing send, search, archive, delete, label management, and other essential operations.