MCP Headless Gmail Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gmail_get_recent_emailsA | Get the most recent emails from Gmail (returns metadata, snippets, and first 1k chars of body) |
| gmail_get_email_body_chunkB | Get a 1k character chunk of an email body starting from the specified offset |
| gmail_send_emailC | Send an email via Gmail with optional file attachments |
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 has a clearly distinct purpose: gmail_get_email_body_chunk retrieves specific content from an email, gmail_get_recent_emails fetches metadata and previews of multiple emails, and gmail_send_email handles outgoing messages. There is no overlap in functionality that could cause confusion.
All tools follow a consistent 'gmail_verb_noun' pattern with snake_case, making them predictable and easy to understand. The naming convention is uniform across all three tools.
With only 3 tools, the server feels thin for a Gmail integration, lacking essential operations like searching emails, managing labels, or deleting messages. While the tools cover basic read and send functions, the scope is limited compared to typical email management needs.
The toolset has significant gaps for a Gmail server: there is no way to search or filter emails beyond recent ones, no ability to update or delete emails, no label management, and no full email retrieval beyond chunks. This incomplete surface will likely cause agent failures in common email workflows.