@injaan.dev/ms365-email-cli-mcp
Related Servers
Alternatives to @injaan.dev/ms365-email-cli-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes a Microsoft 365 mailbox via the Model Context Protocol, enabling AI assistants to search, read, and download emails and attachments, and optionally send mail.-
- AlicenseAqualityDmaintenanceProvides a minimal Microsoft 365 MCP server with fourteen hand-written tools for email, people, and drafts, designed to fit small local models.14MIT
- FlicenseAqualityDmaintenanceA lightweight MCP server for personal Microsoft Outlook/Hotmail accounts, enabling email search, reading, attachment management, and folder operations via Microsoft Graph API with OAuth device-code flow.61-
- AlicenseBqualityBmaintenanceAn MCP server that lets an AI assistant work in a user's Microsoft 365: mail, calendar, contacts, OneDrive and SharePoint files, Teams chats and channels, Planner, OneNote and To Do, all through Microsoft Graph. It signs in as the user (delegated OAuth), so it reaches only what that user can already reach. Run it locally over stdio, or host it as a remote server with per-user sign-in.971MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for reading, searching, sending, and managing emails via IMAP/SMTP, with tools like list_emails, read_email, search_emails, send_email, get_attachment, get_account_info, and mark_email_read.31 npmISC
- FlicenseAqualityCmaintenanceA 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.6-
TDQS
Scored across 10 tools
Each tool targets a distinct email operation: listing, reading, threading, read status, searching, sending, replying, reply-all, and attachments. Even similar tools like list_emails and list_unread_emails are clearly separated by filter, so no real ambiguity.
Most tools follow a verb_noun pattern (list_emails, read_email, mark_read, search_emails, send_email, reply_all), but 'thread' and 'attachment' are nouns, and 'reply' is a bare verb. The naming is readable but not perfectly uniform.
With 10 tools, the server is well-scoped for an email CLI. Each tool addresses a core email workflow (read, list, search, send, reply, manage attachments), without excess or superficial additions.
The surface covers the main email lifecycle: list, read, search, send, reply, and attachments. Minor gaps exist such as no mark_unread, delete, or folder management, but these are not critical for basic email operations and can be worked around.