This is deliberately one job — compose somewhere, send from there — and AWS SES is the right backend for it if you already have a verified domain. The failure mode to know about is SES itself: an unverified sender address is rejected at the service, not by this server, so verify before you wire it up.
A small MCP server that puts AWS Simple Email Service behind a tool call, so a draft written in your editor gets sent without a copy-paste into a mail client. It handles both plain text and HTML bodies and supports the recipient fields you would expect from a real send.
Sending a message with a subject and either a text or HTML body, adding CC and BCC recipients, setting a reply-to address, and choosing the sender — subject to that address being verified in SES. Full request and response logging is written out for debugging a rejected send.
An AWS SES account with a verified domain or verified sender addresses, plus AWS credentials with SES permissions: `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_REGION`, `SENDER_EMAIL_ADDRESS` and `REPLY_TO_EMAIL_ADDRESSES`. Node.js, with `npm install` and `npm run build` from a clone; the client then launches `node` against `build/index.js`. The same values can be passed as command-line flags instead of environment variables, which is what the Cursor setup uses.
One command plus a key — npx -y @smithery/cli install @omd01/aws-ses-mcp --client claude, then supply credentials