outlook-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_startA | Start the Outlook authentication flow. IMPORTANT: Only call this tool when you receive an authentication error (e.g. 'Not authenticated') from another tool, or when the user explicitly requests re-authentication. Do NOT call this proactively before using other Outlook tools — they automatically use the stored token. If a valid token already exists, this returns immediately without starting a new auth flow. |
| auth_pollA | Check if the authentication is complete. Only call this after auth_start returned a verification URL and the user has completed sign-in on the Microsoft website. Do NOT call this unless you just ran auth_start and it returned a code/URL for the user to visit. |
| send_emailA | Send an email immediately via Microsoft Outlook. Supports To, CC, BCC, plain text or HTML body, and file attachments (max 3 MB each). |
| save_draftA | Save an email as a draft in Microsoft Outlook without sending it. Recipients are optional — a Draft can be started with just a subject and body, with recipients added later via update_draft. Supports CC, BCC, plain text or HTML body, and file attachments (max 3 MB each). |
| update_draftA | Partially update a saved Draft. Only fields you supply are changed — omitted fields are left as-is on the server. Use list_messages(folder: 'drafts') to find Draft IDs. |
| send_draftA | Send a previously saved Draft by its message ID. Use save_draft to create a Draft, update_draft to edit it, then send_draft to transmit it to Recipients. |
| list_group_membersB | List all members of a Microsoft 365 Group. Useful for finding email addresses of everyone in a group before sending. |
| list_distribution_groupsB | List mail-enabled Distribution Groups in the organisation (classic distribution lists). Each group has a single email address that delivers to all its members. |
| list_contactsA | List personal Contacts from the authenticated user's Outlook address book. Optionally filter by name or email. |
| list_contact_foldersA | List the user's contact folders (contact lists) from Outlook, such as 'My ThailandPostMart - Dev'. To see contacts inside a folder, use list_contacts with the folderId. |
| list_usersA | Search or list Azure AD users in the organisation. Use 'search' to find users by name or email. Without 'search', returns all users paginated. Useful for finding recipient email addresses. |
| list_mail_foldersA | List all mail folders in the authenticated user's mailbox, including custom folders. Returns folder IDs needed for list_messages with non-standard folders. |
| list_messagesA | List Messages from a mail folder. Use folder 'inbox', 'drafts', 'sentitems', or 'deleteditems' (well-known names), or pass a folderId from list_mail_folders. Supports full-text search and OData filter — but NOT both at once. |
| get_messageA | Read the full content of a single Message by ID. Returns body (plain text or HTML), all recipients, and attachment metadata (name, size, type — not file content). |
| reply_messageB | Reply to a Message. Thread history is preserved automatically. The reply is sent immediately. |
| forward_messageC | Forward a Message to one or more new Recipients. Optionally include a comment prepended to the forwarded message. |
| mark_messageC | Mark a Message as read or unread. |
| delete_messageA | Delete a Message or Draft by moving it to the Deleted Items folder. The message is NOT permanently erased — it can be recovered from Deleted Items. |
| reply_all_messageB | Reply to a Message, sending immediately to the sender and all original Recipients. Thread history is preserved automatically. |
| reply_draftA | Create a reply Draft addressed to the original sender, instead of sending immediately. Review or edit it, then use send_draft. Returns the created Draft's id, subject, and to/cc. |
| reply_all_draftA | Create a reply-all Draft addressed to the sender and all original Recipients, instead of sending immediately. Review who it's going to, then use send_draft. Returns the created Draft's id, subject, and to/cc. |
| forward_draftA | Create a forward Draft to new Recipients, instead of forwarding immediately. Review or edit it, then use send_draft. Returns the created Draft's id, subject, and to/cc. |
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 22 tools
Each tool targets a fairly distinct resource+action, and the message/draft suffix pattern clearly separates immediate-send operations (reply_message, forward_message) from draft-creating ones (reply_draft, forward_draft). The closest overlaps are reply_message vs reply_all_message and send_email vs send_draft, but descriptions make the intent clear enough that misselection risk is low.
Nearly all tools follow a clean verb_noun snake_case convention (list_messages, get_message, send_draft, delete_message), which is very predictable. The only deviations are the two auth tools (auth_start, auth_poll) that use noun_verb order, a minor inconsistency in an otherwise uniform set.
22 tools is on the heavy side for a mailbox client, with a large cluster of near-sibling reply/forward variants (immediate vs draft, single vs all) that multiply the surface. Each tool does earn a place in the draft workflow, so it is defensible but not tightly scoped.
Core mail lifecycle is well covered: list/read, send, reply, reply-all, forward, draft create/update/send, delete, mark read/unread, plus folder, contact, and user lookup for addressing. Notable gaps remain — attachments are metadata-only (no download of file content), no move/copy between folders, and no folder creation — but agents can work around these for most tasks.