outlook-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OUTLOOK_MCP_CLIENT_ID | Yes | Azure application client ID for Microsoft Graph API access. |
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 |
|---|---|
| search_emailsA | Search emails using Graph KQL syntax. |
| read_emailB | Read full body + headers of one message. |
| list_attachmentsB | List attachments on a message. Returns list of {id, name, contentType, size}. |
| download_attachmentB | Download an attachment to save_path (absolute path; parent dirs auto-created). |
| mark_as_readA | Mark a message as read (default) or unread. Returns {id, isRead}. |
| move_emailA | Move a message to a folder. folder = well-known name (archive, inbox, deleteditems, junkemail, sentitems, drafts) or a folder ID returned by another Graph call. Returns {id, parentFolderId}. |
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 6 tools
Each tool targets a distinct operation (downloading, listing, marking, moving, reading, searching) with no overlap. The resource (email or attachment) and action are clearly separated.
All tools follow a consistent verb_noun pattern in snake_case (download_attachment, list_attachments, etc.), making it predictable and easy to navigate.
6 tools is a well-scoped number for an email client MCP server. It covers the essential operations without being bloated or too sparse.
The set covers reading, searching, moving, marking read, and attachment handling. Missing send/compose and delete operations, which are common but not critical for a read-focused server.