MCP Email Server (Gmail)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server to listen on. Most hosting providers set this automatically. | |
| MCP_AUTH_TOKEN | No | Secret auth token required when running the remote HTTP server (Option B). Generate with `openssl rand -hex 32`. | |
| GOOGLE_CLIENT_ID | Yes | Google OAuth Client ID from your Google Cloud credentials. | |
| GOOGLE_CLIENT_SECRET | Yes | Google OAuth Client Secret from your Google Cloud credentials. | |
| GOOGLE_REFRESH_TOKEN | Yes | Refresh token printed by the authorize script, used to send email from your Gmail account. |
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 |
|---|---|
| send_emailA | Send an email via Gmail, optionally attaching a file from the attachments folder (e.g. a resume PDF). Always show the user the drafted subject/body/recipient and get confirmation before calling this. |
| list_attachmentsA | List files available in the attachments/ folder (e.g. resume.pdf) that can be attached to an email. |
| get_profileA | Get the user's resume/profile summary (skills, education, experience) stored in profile.md. Use this to tailor cover letters and outreach emails. |
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 targets a clearly distinct resource and action: sending email, listing attachment files, and retrieving the user profile. There is no overlap in purpose, so an agent can easily select the right tool.
All tool names follow a consistent snake_case verb_noun pattern: send_email, list_attachments, get_profile. The naming is predictable and readable throughout.
Three tools is slightly thin for a server labeled as a Gmail email server, but each tool earns its place for the apparent send-focused outreach workflow. More email management tools would be expected for a broader Gmail integration.
The surface covers sending emails, listing attachments, and retrieving profile context, but obvious Gmail operations like reading, searching, replying, or managing drafts are missing. These gaps are notable for an email server, though the described outreach use case is partially supported.