gmail-mcp-send-to-list-only
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMAIL_TOKEN_FILE | Yes | Path to the token file where OAuth token is stored. | |
| GMAIL_SENDER_EMAIL | Yes | Gmail address that is authorized and used as sender. | |
| GMAIL_MAX_ATTACHMENTS | No | Maximum number of attachments per message. | 10 |
| GMAIL_ALLOWED_RECIPIENTS | Yes | Comma-separated list of allowed recipient email addresses. | |
| GMAIL_CLIENT_SECRET_FILE | Yes | Path to the Google OAuth client secret JSON file. | |
| GMAIL_MAX_ATTACHMENT_BYTES | No | Maximum size per attachment in bytes. | 25000000 |
| GMAIL_ALLOWED_ATTACHMENT_ROOTS | No | Optional comma-separated list of directories from which attachments can be sent. | |
| GMAIL_MAX_TOTAL_ATTACHMENT_BYTES | No | Maximum total size of all attachments in one message in bytes. | 25000000 |
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 |
|---|---|
| gmail_list_allowed_recipientsA | List the only recipient IDs and addresses that this process can use. |
| gmail_send_emailC | Send one email to a non-empty allowed subset in visible To. |
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 are clearly distinct: one lists allowed recipients, the other sends an email. There is no overlap in their purposes, so an agent would not confuse them.
Both tool names follow the same pattern: 'gmail_' prefix, then a verb ('list' or 'send') and an object. This consistent snake_case naming makes the toolset predictable.
With only 2 tools, the set is minimal, but the server's narrow purpose (send to a restricted list) justifies this. It is slightly under the typical 3-15 range but reasonable for the scope.
The domain is fully covered: the list tool lets the agent discover allowed recipients, and the send tool performs the actual email sending. No essential operations are missing for a 'send-to-list-only' server.