@striderlabs/mcp-gmail
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 |
|---|---|
| gmail_sendA | Send an email from the user's Gmail account. Use this when the user wants to send an email to someone. |
| gmail_searchA | Search emails in the user's Gmail inbox using Gmail search syntax. Use this to find specific emails. |
| gmail_readB | Read the full content of a specific email by its message ID. |
| gmail_listB | List recent emails from the inbox. Use this to see what emails the user has received. |
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 4 tools
Each tool has a unique and clearly defined purpose: listing inbox, sending, searching, and reading specific emails. There is no overlap in functionality.
All tool names follow a consistent 'gmail_<verb>' pattern (list, send, search, read), making them predictable and easy to distinguish.
With 4 tools, the server is well-scoped for basic Gmail operations. It covers the most common actions without being overly minimal or bloated.
The set covers core email workflows (read, send, list, search) but lacks update/delete or draft management, which are common in email systems. Minor gap.