Email MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_PASSWORD | Yes | Your 16-digit app password (for Gmail, generate an app password in account security settings) | |
| EMAIL_ADDRESS | Yes | Your email address |
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 |
|---|---|
| list_recent_emailsA | List the most recent emails in the inbox (without bodies). |
| read_emailA | Read the full body content of a specific email by ID. |
| summarize_emailB | Get an AI summary of a specific email by ID (Internal Server-Side Summarization Demo). |
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 serves a distinct purpose: listing emails, reading full content, and summarizing. No overlap in functionality, making it easy for an agent to select the correct tool.
All tools follow a consistent verb_noun pattern with snake_case naming (list_recent_emails, read_email, summarize_email), providing clear and predictable naming.
With only 3 tools, the server is on the thin side but acceptable for a focused demo or specialized task. However, it may feel insufficient for broader email management.
The server lacks essential email operations like sending, deleting, or searching, limiting its usefulness. It only covers reading and summarizing, leaving significant gaps for typical email workflows.