MCP Aruba Email & Calendar Server
Related Servers
Alternatives to MCP Aruba Email & Calendar Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, send, organize, and search emails across multiple IMAP/SMTP mailboxes.756 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to read, search, compose, and send emails by connecting to any IMAP/SMTP provider. It supports comprehensive mailbox management, including draft handling and message deletion, directly through natural language.10239 npm11MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and manage email, contacts, and calendar data over JMAP/CalDAV/WebDAV, including searching, sending, threading, attachments, contacts, events, and mailbox operations.MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to send, read, and manage emails via SMTP and IMAP, with support for attachments, threads, and mailbox organization.1681 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with email accounts via IMAP and SMTP, supporting mailbox listing, email search, retrieval, sending, and management.MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to email accounts via IMAP/SMTP, enabling reading, searching, sending, and organizing emails with features like smart drafts, scheduling, and attachment handling.108 npm2MIT
TDQS
Scored across 19 tools
Most tools target clearly distinct resources and actions (list/read/search email, create/list/respond/delete event). The one real overlap is download_attachment vs save_attachment, which both fetch an attachment's bytes; the description mitigates this by declaring save_attachment preferred, but an agent could still hesitate. read_email vs get_raw_email is also a mild boundary case.
Nearly all tools follow a snake_case verb_noun pattern (accept_calendar_event, list_emails, set_email_signature). Verb choices vary slightly (read_email vs get_email_attachments vs list_email_signatures), but the convention remains readable and predictable.
19 tools is at the upper edge of the ideal range but each maps to a real operation across two domains (email and calendar). The three signature tools (set/get/list) are the least essential and inflate the count slightly.
Email coverage is strong (send, reply, list, read, search, attachments, raw export, bounces, signatures) and calendar covers create/list and all RSVP actions plus delete. Gaps remain: no update_calendar_event, no way to list mail folders (leaving the folder parameter a dead end), and no delete/move/forward for email.