outlook-mcp
Related Servers
Alternatives to outlook-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server providing full control over Outlook.com, Hotmail, Live, or Microsoft 365 email via Microsoft Graph API, enabling reading, searching, sending, and managing messages and folders securely.1MIT
- FlicenseAqualityCmaintenanceAn MCP server that enables reading and managing Microsoft 365 / Outlook emails through Microsoft Graph API, allowing users to list, search, send, draft, and authenticate using device code flow.17-
- FlicenseNot gradedqualityCmaintenanceMCP server that connects an Outlook mailbox to view recent emails, read specific messages, and send replies using Microsoft Graph.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Microsoft Outlook that enables searching, sending, and managing mail and calendar via the OWA REST API using browser-session authentication, with no Azure AD app registration required.MIT
- AlicenseBqualityAmaintenanceMCP server that provides 62 tools to manage Outlook mail, calendar, contacts, and tasks for personal Microsoft accounts via Microsoft Graph API.71995 PyPI45MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that uses Microsoft Entra OAuth 2.0 On-Behalf-Of flow to access Microsoft Graph for Outlook data, enabling email, calendar, and contacts interactions via MCP tools.-
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.