Gmail Sender MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_CLIENT_ID | Yes | Your Google OAuth 2.0 Client ID | |
| GMAIL_CLIENT_SECRET | Yes | Your Google OAuth 2.0 Client Secret |
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 |
|---|---|
| sendEmailB | Send an email through Gmail. Requires OAuth authentication. |
| createDraftA | Create an email draft in Gmail. Requires OAuth authentication. |
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: creating a draft vs sending an email. An agent can easily differentiate between them.
Both tool names follow a consistent verb_noun pattern using camelCase (createDraft, sendEmail), demonstrating strong naming consistency.
With only 2 tools, the server is tightly scoped to its purpose of sending emails and creating drafts. Each tool earns its place.
The server covers core email sending and draft creation but lacks common operations like listing, deleting drafts, or managing attachments. There are notable gaps for a full workflow.