Gmail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTION_API_KEY | No | Your Notion API key for retrieving style guidelines. | |
| NOTION_STYLE_GUIDE_PAGE_ID | No | The ID of the Notion page containing your email writing style guide. |
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 |
|---|---|
| get_unread_emailsC | Retrieves unread emails from Gmail inbox with sender, subject, snippet, and thread information |
| create_draft_replyC | Create draft reply to an email in thread |
| get_style_guideB | Retrieves the email writing style guide from Notion |
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
The tools have distinct purposes (draft replies, get style guide, get unread emails), but 'create_draft_reply' and 'get_unread_emails' could be confused as both relate to email handling, while 'get_style_guide' stands apart as a Notion resource. Some overlap exists in the email domain, but descriptions help clarify boundaries.
The naming follows a consistent verb_noun pattern (create_draft_reply, get_style_guide, get_unread_emails) with 'get' used for two tools and 'create' for one. This is mostly consistent with minor deviations, as the verbs align well with the actions described.
With only 3 tools for a Gmail server, the count feels too thin for the apparent scope. A Gmail domain typically requires more operations like sending emails, managing labels, or searching beyond unread emails, making this set under-scoped and likely incomplete.
There are significant gaps in the tool surface for a Gmail server. Missing core operations include sending emails, searching emails beyond unread, managing labels or folders, and accessing full email content. This will cause agent failures when trying to perform common email tasks.