Wraps Email for Amazon SES
Related Servers
Alternatives to Wraps Email for Amazon SES
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityDmaintenanceMCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.16MIT

fagents-mcpofficial
AlicenseNot gradedqualityCmaintenanceMCP server that enables Claude Code agents to send and read emails via SMTP/IMAP with per-agent credential isolation and audit logging.MIT- AlicenseBqualityAmaintenanceThe email API your AI agent can actually use. A Model Context Protocol server for Send16 that gives Claude, Cursor, and any MCP client 79 tools to send transactional & marketing email, manage contacts, audiences, segments, automations, templates, the inbox, suppressions, and webhooks.7936 npmMIT
- AlicenseBqualityCmaintenanceDisposable email MCP server for autonomous AI agents. Create labeled temporary inboxes, wait for verification emails, extract OTP codes and confirmation links — zero human intervention required.6MIT
TDQS
Scored across 7 tools
Each tool addresses a distinct aspect: sending, listing sends, retrieving event logs, checking domain verification, checking suppression list, checking setup status, and estimating cost. No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun snake_case pattern (send_email, list_recent_sends, get_email_event_log, verify_domain_status, list_suppressions, get_setup_status, estimate_cost). This predictability aids agent routing.
With 7 tools covering send, monitor, diagnose, and plan, the surface is appropriately scoped for an email service without redundancy or bloat.
The set covers the core workflow: send, verify identity, check suppression, observe delivery events, and estimate cost. Missing administrative operations (e.g., adding domains) are reasonable omissions given the server's focus on sending and observability.