ox-mcp
Related Servers
Alternatives to ox-mcp
- AlicenseNot gradedqualityDmaintenanceLocal MCP server for macOS Mail reads plus visible unsent compose, reply, and forward drafts, and constrained single-message moves.MIT
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP clients to search, read, and manage a self-hosted mailbox over JMAP, including attachments with OCR, sending, drafts, and contacts.10129 npmMIT
- AlicenseBqualityCmaintenanceA comprehensive MCP server that aggregates email, calendar, and contacts across Google, Microsoft, Zoho, and IMAP/SMTP services, designed for headless environments with OAuth device flow support.1352 npm3MIT
- AlicenseAqualityDmaintenanceMCP server that enables email management (send, read, search, delete, etc.) via IMAP/SMTP, compatible with Gmail, Outlook, Yahoo, iCloud, and other standard mail servers.1129 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for reading and sending emails via IMAP and SMTP, designed for Zimbra and any standard mail host.4 npm1ISC
- -licenseNot gradedqualityBmaintenanceSecure MCP server for Microsoft Exchange. It enables authorized users to list, search, read, download attachments, send, and reply to email via EWS with strict access control and audit.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to work with a Microsoft Exchange mailbox over EWS, covering mail reading, searching and filing, calendar viewing and editing, free/busy checks, meeting-room discovery and booking, and sending mail with attachments, signatures and delayed delivery. Includes dry-run previews, recoverable deletes, attachment sandboxing, and read-only or no-send modes.MIT
TDQS
Scored across 33 tools
Tools are cleanly partitioned into email_*, calendar_*, and contact_* groups with distinct actions. A few email tools overlap slightly in effect (email_move vs email_archive vs email_mark_spam all relocate a message, and email_flag vs email_mark_read both set flags), but the descriptions clarify the boundaries well.
A consistent domain_verb_noun convention (email_create_folder, calendar_create_event, contact_create) dominates, with implied-noun variants (email_send, email_reply, email_delete) that stay readable. Minor deviation is the sub-resource prefix pattern in email_filter_list/email_filter_create/email_filter_update and email_list_folders, but overall predictable.
33 tools is on the heavy side, but the server genuinely spans three substantial domains (mail, calendar, contacts), and nearly every tool maps to a real operation. Slightly above the ideal range for a single MCP server but justified by scope.
Email coverage is strong (list/read/send/reply/draft/search/folders/flags/filters), and calendar covers the full event lifecycle including invitations. Minor gaps remain: no email_filter_delete, and contacts lack update/delete operations, but core workflows are covered.