Email-MCP
Related Servers
Alternatives to Email-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to send emails via SMTP, supporting simple and custom emails with attachments and CC/BCC, plus connection testing.327MIT
- AlicenseAqualityBmaintenanceAn MCP server providing comprehensive email capabilities via IMAP and SMTP, enabling AI assistants to read, search, send, manage, schedule, and analyze emails across multiple accounts.521,447 npm128LGPL 3.0
- AlicenseAqualityDmaintenanceAn MCP server providing comprehensive email capabilities via IMAP and SMTP, enabling AI assistants to read, search, send, manage, schedule, and analyze emails across multiple accounts.491,447 npmLGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that empowers AI agents to securely send emails via SMTP, supporting plain text, HTML, and attachments.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to validate email addresses and send emails via SMTP with zero external dependencies.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server enabling AI assistants to manage Gmail through natural language, including sending, reading, searching, labeling, and handling attachments with auto authentication.1MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose of sending emails.
The naming is trivially consistent as there is only one tool. The tool name 'mcp_email_send' follows a clear pattern with a prefix, resource, and verb, though consistency cannot be assessed across multiple tools.
A single tool for an email server is too few for the apparent scope. Email management typically requires operations like reading, listing, deleting, or searching emails, making this set feel incomplete and thin.
The tool set is severely incomplete for an email domain. It only provides a send function, lacking essential operations such as receiving, reading, listing, or managing emails, which will cause significant agent failures in handling email-related tasks.