gmail-mcp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listEmailsB | List emails from Gmail with subject, sender, and body in Markdown format. Optionally filter and summarize results. |
| getEmailContentC | Retrieve the full content of an email from Gmail. |
| sendEmailC | Send an email from Gmail. |
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 3 tools
Each tool has a clearly distinct purpose: getEmailContent retrieves a specific email's full content, listEmails lists emails with optional filtering/summarization, and sendEmail sends emails. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (getEmailContent, listEmails, sendEmail) with clear, descriptive names. The naming style is uniform throughout the set, enhancing readability and predictability.
With only 3 tools, the set feels thin for a Gmail integration, as it lacks operations like deleting emails, marking as read/unread, or managing labels. While the core functions are present, the scope is limited compared to typical email management needs.
The tools cover basic read (get, list) and write (send) operations, but there are notable gaps in the email lifecycle, such as updating email status (e.g., delete, archive, mark as read) or handling attachments. This could lead to agent workarounds for common email tasks.