outlook-mcp
Related Servers
Alternatives to outlook-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables interaction with Outlook Web through its internal API, supporting email search, folder listing, email retrieval, read state changes, calendar events, and reply drafts without Microsoft Graph or COM.71MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read, search, locally index, and draft Outlook mail and calendar events through Outlook Web's first-party device-code sign-in and internal JSON API, without Azure app registration, Graph, or admin consent. Sending requires a human-issued one-time approval nonce bound to the exact draft content.AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceReads and searches your local Microsoft Outlook desktop mailbox via COM, supporting folder listing, message/thread retrieval, attachment saving, bulk export, and draft creation without sending, requiring no OAuth or admin consent.-
- AlicenseAqualityBmaintenanceEnables Claude, Codex and other MCP clients to browse folders, search, read, send, reply to, forward, move, flag and delete Microsoft 365 / Outlook.com mail through the Microsoft Graph API, including attachment downloads, newsletter unsubscribe and inbox rules. Signs in with the OAuth device code flow and keeps the refresh token in the OS keychain, with an optional read-only mode that removes every mutating tool.26136 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables headless reading of Microsoft 365 mail, calendar, Teams chats and channels, OneDrive, SharePoint and OneNote over Microsoft Graph using a single password-plus-TOTP sign-in. No app registration or admin consent is needed, since it brokers pre-consented first-party clients from one FOCI refresh token.307 PyPI2MIT
- AlicenseBqualityBmaintenanceConnects MCP clients such as Claude Desktop, Cursor, and Hermes Agent to the classic Outlook profile signed in on the same Windows PC, enabling mail search and reading, saving replies to Drafts, sending email, and listing or creating calendar events and tasks. Everything runs locally over stdio with tiered read/write/destructive gates and an audit log, so the mailbox is never uploaded to a third-party API.12MIT
TDQS
Scored across 40 tools
Tools are cleanly separated along resource+action lines: message read paths (list/search/get/get_thread), draft lifecycle (create/update/send_draft vs send_message/reply/forward), and folder/calendar/contact operations never collide. Near-overlaps like delete_messages vs move_messages or search_people vs list_contacts are explicitly disambiguated in the descriptions, and even attachment listing vs downloading is distinguished.
Every tool follows a strict snake_case verb_noun pattern (list_folders, get_message, create_event, delete_contact, mark_messages_read). Plurals and resource nouns are used consistently so the target object is always obvious from the name.
40 tools is well above the well-scoped range; the surface is large because it spans mail, drafts, folders, attachments, calendar, contacts and categories in one server. Each tool is individually justified, but the volume forces an agent to sift through a broad catalog for routine tasks.
Lifecycle coverage is strong: mail read/search/send/draft/reply/forward/flag/categorize/move/copy/delete, folder CRUD+move, attachment add/remove/list/download, event CRUD plus respond_to_event, and contact CRUD plus directory search. Remaining gaps are peripheral (inbox rules, out-of-office, creating/deleting categories or calendars, bulk event ops).