smailr-mcp
Related Servers
Alternatives to smailr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects any IMAP/SMTP mailbox to AI agents via MCP, enabling email read, search, send, reply, and management through natural language.3 npmMIT
- AlicenseBqualityBmaintenanceEnables users to manage email accounts via IMAP/SMTP, including reading, searching, sending emails with attachments and calendar invites, all through natural language interactions with MCP-compatible clients.14MIT
- FlicenseBqualityDmaintenanceEnables AI models to send, receive, search, and manage emails via SMTP/IMAP, including support for attachments, contacts, and advanced search.18-
- AlicenseBqualityAmaintenanceConnects MCP clients to any IMAP/SMTP email account, enabling email search, reading, sending, replying, forwarding, flagging, moving, and folder management via natural language.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, search, and manage email via IMAP, and send emails with attachments via SMTP, using natural language commands.301 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables secure mailbox access and email management via IMAP/SMTP, with tools for reading, searching, organizing, sending, and deleting emails, designed for local use and compatible with MCP clients like ChatGPT.1MIT
TDQS
Scored across 23 tools
Most tools are clearly resource-action pairs, but get_quota and get_stats both cover storage/account usage and list_mails/search_mails could be confused when searching a single mailbox. These are minor boundary cases; the rest are distinct.
All tools use lowercase snake_case verb_noun names (list_, create_, get_, update_, delete_, search_, send_, upload_, check_). Naming is uniform and predictable across all 23 tools.
23 tools is within the heavy range for an MCP server. The email domain is broad enough to justify many of them, but the count feels slightly bloated because several resource areas have only partial operations.
Mailboxes and mails have solid lifecycle coverage, but contacts, labels, and folders only support list/create, while rules and signatures are read-only. Agents cannot update or delete these secondary resources, which is a significant gap for full email management.