Graph Mail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SystemRoot | Yes | Windows system root directory (e.g., C:\Windows). Required for system-level utilities. | |
| USERPROFILE | Yes | Path to the current Windows user's profile directory. Required for resolving user-specific paths. | |
| LOCALAPPDATA | Yes | Path to the local application data directory for the current Windows user. Used for token cache, Edge profile, and runtime state. |
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 |
|---|---|
| mail_auth_statusA | Return authentication status, expiry, unexpected-scope warnings, and the next login action without exposing tokens. |
| mail_list_foldersD | List folders in the selected mailbox scope. |
| mail_search_messagesA | Search messages safely. Prefer subject for a known title; query is full-text and may match message bodies. |
| mail_get_messageB | Read one message by Graph ID, immutable ID, or internetMessageId with an explicit body mode. |
| mail_get_threadA | Reconstruct a bounded mailbox-local conversation with complete per-message headers and the requested body mode. Embedded forwarded chains are not separate messages. |
| mail_list_attachmentsC | List metadata for a message attachments collection. |
| mail_get_attachmentC | Get bounded attachment metadata/text/base64 content. |
| mail_create_draftC | Create a new/reply/reply-all/forward draft without sending. |
| mail_update_draftB | Update an MCP-owned draft after registry and Graph preflight. |
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 9 tools
Most tools are clearly distinct by resource and action: folders, auth, messages, threads, attachments, drafts. There is slight potential confusion between mail_get_message and mail_get_thread (both retrieve messages), but descriptions clarify the difference (single message vs conversation). mail_list_attachments and mail_get_attachment are distinct (list vs get). Overall, boundaries are clear.
All tools follow the exact pattern mail_<verb>_<noun>, using snake_case throughout. Verbs are consistent: list, auth, search, get, create, update. This is a highly predictable and consistent naming convention.
Nine tools is well within the ideal range (3-15). Each tool serves a distinct purpose in the email domain: folder navigation, auth, search, retrieval, thread handling, attachments, and draft management. No redundant or trivial tools.
The tool set covers core email operations: listing folders, searching/reading messages, handling threads, attachments, and creating/updating drafts. A notable missing operation is sending or deleting messages/drafts, which would be expected for a full lifecycle. However, the focus on drafts (without send) may be intentional. Thus, a minor gap.