# Amazon SES MCP server

> Lets AI agents send emails via Amazon SES, manage domain verification, check suppression lists, and handle contact segments through Wraps.

- Repository: https://github.com/wraps-team/wraps-js
- Page: https://hostedmcp.org/servers/wraps-team/email
- Official: yes
- Transport: stdio
- Stars: 1
- License: MIT
- Latest version: 0.11.1

## Install

### Claude Code

```sh
claude mcp add --env 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' email -- npx -y @wraps.dev/mcp
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "env": {
        "WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "email": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "env": {
        "WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"email","type":"stdio","command":"npx","args":["-y","@wraps.dev/mcp"],"env":{"WRAPS_API_KEY":"<YOUR_WRAPS_API_KEY>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "env": {
        "WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add email --env 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' -- npx -y @wraps.dev/mcp
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.email]
command = "npx"
args = ["-y", "@wraps.dev/mcp"]

[mcp_servers.email.env]
WRAPS_API_KEY = "<YOUR_WRAPS_API_KEY>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' email npx -- -y @wraps.dev/mcp
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "env": {
        "WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `WRAPS_API_KEY` | no | yes | Wraps API key (wraps_...) for the contacts, segments, topics, templates, broadcasts, events, workflows, approvals, metrics, inbound and brand-kit tools. Without it the server falls back to the session from `wraps auth login`; with neither, only the AWS tools are registered. |
| `AWS_PROFILE` | no | no | AWS profile to use. Credentials are read locally and never leave the machine. |
| `AWS_REGION` | no | no | Region your Wraps stack is deployed in. Optional only if your active AWS profile supplies one — SES identities are per-region. |
| `WRAPS_ALLOWED_RECIPIENTS` | no | no | Comma-separated addresses the agent may send to. Restricts send_email when write mode is on. |
| `WRAPS_ALLOWED_RECIPIENT_DOMAINS` | no | no | Comma-separated domains the agent may send to. Matching is exact; list subdomains explicitly. |
| `WRAPS_API_URL` | no | no | Wraps API base URL. Defaults to https://api.wraps.dev; set it for a self-hosted control plane. |
| `WRAPS_FROM_EMAIL` | no | no | Default from address for send_email. Must be a domain verified in your SES account. |
| `WRAPS_HISTORY_TABLE_NAME` | no | no | DynamoDB table holding email history. Defaults to wraps-email-history. |
| `WRAPS_ORG_ID` | no | no | Organization id to act in when using a `wraps auth login` session that belongs to several organizations. |
| `WRAPS_WRITE_ENABLED` | no | no | Set to true to enable the send_email tool. Read-only by default. |

## Tools (7)

- `send_email`: Send a transactional email via your AWS SES account. Requires WRAPS_WRITE_ENABLED=true. The `from` address must be a verified SES identity (an address or domain) in this account and region. The `to` field accepts a single address or an array of addresses.
- `list_recent_sends`: List recently sent emails from your Wraps email history, newest first, at most `limit` messages. The timestamp shown is the send time and is stable across calls. Returns send status, subject, recipient, timestamp, and messageId for each send. Use the messageId with get_email_event_log for full delivery details. The `since` parameter accepts a full ISO 8601 datetime string (e.g., 2024-01-01T00:00:00Z). (read-only)
- `get_email_event_log`: Get the full delivery event log for a specific email by its messageId. Returns all SES events: Send, Delivery, Bounce, Complaint, Open, Click. (read-only)
- `verify_domain_status`: Check the verification and DKIM status of a sending domain in your AWS SES account. Returns whether the domain is verified for sending and its DKIM configuration status. (read-only)
- `list_suppressions`: List addresses on your AWS SES account-level suppression list, or check a single address with `email`. SES silently drops mail to suppressed addresses, and sending to them damages your sending reputation, so check before sending to an address you have not sent to recently. To determine whether one specific address is suppressed, always pass `email` — that is an exact lookup. The listing is paginated and states explicitly when it is truncated; a truncated listing is never proof that an address is unsuppressed. Optionally filter the listing by reason (BOUNCE or COMPLAINT). (read-only)
- `get_setup_status`: Check this AWS SES account's sandbox status and get a recommended next action for getting a first send out. Read-only — makes no changes to your AWS account. (read-only)
- `estimate_cost`: Estimate the monthly cost of sending email with Wraps + AWS: the flat Wraps plan fee and an itemized AWS bill (SES, EventBridge, SQS, Lambda, DynamoDB, dedicated IP, WAF). Use this instead of calculating by hand — the cost model has several interacting variables, including which SES pricing plan the AWS account is on. Requires no AWS credentials. (read-only)

## FAQ

### How does the server handle my AWS credentials?

The server runs locally via stdio, ensuring your AWS credentials never leave your machine.

### What is required to use the API-backed tools?

You will need a WRAPS_API_KEY or a session obtained through 'wraps auth login'.

### Can I use this with any SES account?

Yes, the server is compatible with any SES account.

### What do I need to see recent sends or email event logs?

You must have the Wraps event pipeline deployed using the Wraps CLI.
