outlook-mcp
Related Servers
Alternatives to outlook-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude or any MCP client to read, search, draft, and send approved email, triage and clean up messages, unsubscribe, and manage inbox rules in Outlook.com or Microsoft 365 mailboxes through Microsoft Graph.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to read, search, draft, send, reply to, forward, and organize Microsoft Outlook mail via Microsoft Graph, with safe-by-default read-only operation and browser-based sign-in.15108 npmMIT
- AlicenseAqualityDmaintenanceMCP server that connects Claude to Microsoft 365 mail for inbox triage, search, classification, and idempotent rule provisioning via Microsoft Graph, with device-code auth and read-only default.61MIT
- AlicenseAqualityCmaintenanceA local MCP server that gives Claude read/write access to a personal Hotmail/Outlook.com mailbox via the Microsoft Graph API, exposing tools for listing, searching, sending, and drafting emails.65 npmMIT
- AlicenseAqualityBmaintenanceEnables Claude to read, search, organize, and draft email in an Outlook/Microsoft 365 mailbox via Microsoft Graph, while pseudonymizing personal data (names, emails, phone numbers, national ID numbers, IBANs, addresses) into reversible tokens before anything reaches the model. Supports folder listing, message search, flagging, categorizing, moving, and draft creation/editing, but cannot send mail since it only requests Mail.ReadWrite and User.Read permissions.12MIT
- AlicenseAqualityCmaintenanceGives Claude Code access to Outlook Mail, Calendar, and Contacts via Microsoft Graph, with safety-first defaults (no sending, no hard deletes, every mutation logged). Supports multiple Microsoft accounts through a PKCE OAuth flow.21MIT
TDQS
Scored across 26 tools
Most tools have clearly distinct resource+action targets, and the descriptions explicitly cross-reference related tools (e.g. block_sender/delete_rule, get_unsubscribe_info/unsubscribe, delete_message/bulk_action). The main soft overlaps are the single-message mutators (mark_read, flag_message, move_message, delete_message) versus bulk_action, which applies the same actions to a search result set, plus find_newsletters/mail_digest both surfacing newsletter hints; descriptions mitigate these but an agent could still pick the wrong one at the edges.
The set is uniformly snake_case and overwhelmingly verb_noun (list_messages, search_messages, get_message, send_mail, move_message, create_rule), which makes intent predictable. A handful of deviations exist (auth_status, logout, bulk_action, mail_digest) that are noun-first or verb-less, but they are few and still readable.
At 26 tools this is on the heavy side for a mail client, though the surface is broad (messages, attachments, auth, folders, rules, bulk ops, unsubscribe, digests), so few tools feel truly redundant. The auth trio (login/logout/auth_status) and the unsubscribe trio (get_unsubscribe_info/unsubscribe/find_newsletters) push it past a lean, well-scoped set.
Core lifecycle is well covered: read/search, send, draft, reply, forward, move, flag, read-state, delete (soft and permanent), attachments, folders, rules, and bulk operations. Notable gaps are no way to send or edit an existing draft (create_draft has no companion send_draft/update_draft) and no folder create/rename/delete, but agents can work around these via send_mail and existing well-known folders.