Email

What email does

The email MCP server exposes Amazon SES operations to MCP-compatible clients. It can send a transactional message from a verified SES identity, inspect recent sends and their delivery events, check domain verification and DKIM state, review account-level suppressions, and report SES sandbox setup guidance.

Its cost estimator covers the Wraps plan fee and an itemized AWS estimate for SES, EventBridge, SQS, Lambda, DynamoDB, dedicated IP, and WAF charges. The estimator does not require AWS credentials.

How it works

The server runs locally over stdio and uses the official MCP TypeScript SDK. Configure an MCP client to launch npx -y @wraps.dev/mcp, then provide AWS region and profile settings through the process environment. AWS credentials are read from that environment, allowing the tools to operate against the selected account and region.

Sending is guarded by WRAPS_WRITE_ENABLED=true. The sender address must be a verified SES identity in the configured account and region, and the recipient input can contain one address or an array. Read-only tools do not make changes to the AWS account.

Recent-send queries return messages newest first, with a stable send timestamp, status, subject, recipients, and message ID. Pass that message ID to the event-log tool to retrieve SES events such as send, delivery, bounce, complaint, open, and click.

Setup and configuration

Install and launch the MCP package from an MCP client with a configuration similar to:

{
  "mcpServers": {
    "wraps": {
      "command": "npx",
      "args": ["-y", "@wraps.dev/mcp"],
      "env": {
        "AWS_REGION": "us-east-1",
        "AWS_PROFILE": "your-aws-profile"
      }
    }
  }
}

The package can also run in Docker. Build the repository image with docker build -t wraps-mcp . and start it interactively with docker run -i --rm -e AWS_REGION wraps-mcp.

Enable WRAPS_WRITE_ENABLED=true only when the client should be allowed to call send_email. The sending identity must already be verified by SES. AWS sandbox status can be checked with get_setup_status, which returns a recommended next step for making a first send.

Tools and capabilities

• send_email: Sends transactional email through the configured AWS SES account.
• list_recent_sends: Lists recent messages from Wraps email history, optionally filtered with a full ISO 8601 since timestamp and limited by limit.
• get_email_event_log: Retrieves the complete SES event history for a message ID.
• verify_domain_status: Reports sending verification and DKIM status for a domain.
• list_suppressions: Lists account-level suppressed addresses or performs an exact lookup for one address, with optional BOUNCE or COMPLAINT filtering.
• get_setup_status: Checks SES sandbox status and provides setup guidance without changing the account.
• estimate_cost: Calculates a monthly Wraps plus AWS email estimate without AWS credentials.

Limitations and notes

list_recent_sends and get_email_event_log read history from a Wraps deployment rather than arbitrary SES history. SES silently drops mail sent to suppressed addresses, so check a specific address with the email parameter before sending when appropriate. Suppression listings are paginated; a truncated result cannot establish that an address is absent. Domain verification is region-specific because the sending identity must be verified in the configured SES account and region.