outlook-lite-mcp
Related Servers
Alternatives to outlook-lite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Outlook email through Microsoft Graph API. Supports email management operations like reading, searching, marking as read/unread, and deleting messages through natural language.141 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Microsoft Outlook emails through the Microsoft Graph API, supporting operations like listing, reading, sending, and moving emails.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
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Microsoft 365 Outlook Mail, allowing email operations via natural language.373 npmMIT
- AlicenseAqualityAmaintenanceEnables reading and searching personal Outlook/Hotmail mail, filing into folders, deleting, and unsubscribing from newsletters via Microsoft Graph.965 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to manage Microsoft Outlook email and calendar through the Microsoft Graph API, including reading, sending, searching emails, and handling calendar events.43141 npm30MIT
TDQS
Scored across 13 tools
Most tools map to distinct actions, but the send-side family (rp reply, fw forward, snd send, drf draft) and the retrieval pair (ls list vs find search) overlap enough that an agent must read descriptions carefully to choose correctly. The terse names give almost no signal on their own, so the descriptions carry the disambiguation load.
Names mix cryptic 2–3 letter abbreviations (ls, rd, rp, fw, snd, drf, mv, rm, mk, att, cx) with full English words (find, tag), and there is no verb_noun pattern or shared abbreviation scheme. Without the descriptions, names like 'cx', 'drf', and 'mk' are essentially opaque, making the set feel ad hoc rather than predictable.
13 tools is a well-scoped surface for a lite email client: one tool per core operation (list, search, read, attach, reply, forward, send, draft, move, delete, mark, tag, account). Nothing feels redundant or missing at the count level, though merging draft creation/sending could trim one tool.
The email lifecycle is essentially covered: read, search, send, reply, forward, draft, move, delete, mark, categorize, plus account/folder summary. Minor gaps remain around folder management (creating/renaming folders), explicit CC/BCC handling, and saving attachment content rather than just downloading, but none are blockers for typical workflows.