Lets AI agents send emails via Amazon SES, manage domain verification, check suppression lists, and handle contact segments through Wraps.
Also known as wraps-team/wraps-js, @wraps.dev/mcp
- Stars
- 1
- Tools
- 7
- Downloads, 30 days
- —
- Latest version
- 0.11.1
- Last commit
- Nov 14, 2026
- License
- MIT
What is Amazon SES MCP?
Amazon SES lets AI agents send emails via Amazon SES, manage domain verification, check suppression lists, and handle contact segments through Wraps. It exposes 7 tools, such as send_email, list_recent_sends, get_email_event_log.
Summary generated from the project's README
About Amazon SES MCP server
Managing email communications through Amazon SES is possible directly from an AI agent using this MCP server. It allows developers to send transactional emails, verify domain DKIM status, and check if an account is currently in the SES sandbox. The server runs locally via stdio, ensuring that your AWS credentials remain on your machine.
For users integrating with Wraps, the server provides expanded capabilities for managing contact segments, audience topics, and email templates. You can use tools like list_contacts, create_segment, and get_email_event_log to handle complex marketing workflows. Managing these features requires a WRAPS_API_KEY or a session established through the Wraps CLI.
Beyond basic sending, the server includes tools for monitoring account health, estimating monthly costs, and managing suppression lists. It also supports advanced automation tasks such as creating broadcasts, tracking custom events, and managing automation workflows. This makes it a comprehensive solution for both simple transactional needs and large-scale contact management.
What you can do with it
- 1Send transactional emailsAn AI agent can send a single transactional email using your existing Amazon SES account.
- 2Verify domain configurationCheck the verification and DKIM status of your sending domain to ensure deliverability.
- 3Manage contact segmentsCreate and update audience segments to organize your contact lists effectively.
- 4Monitor email delivery eventsRetrieve detailed logs for specific messages to see if they were delivered, bounced, or opened.
- 5Audit account healthCheck the reputation and sending quotas of your connected AWS accounts.
Written from the project's README. Every use case is checked against a quote from it.
How to install Amazon SES MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Amazon SES MCP in Claude Code
$ claude mcp add --env 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' email -- npx -y @wraps.dev/mcpInstall Amazon SES MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
],
"env": {
"WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
}
}
}
}Install Amazon SES MCP in VS Code
.vscode/mcp.json
{
"servers": {
"email": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
],
"env": {
"WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
}
}
}
}Install Amazon SES MCP in VS Code CLI
$ code --add-mcp '{"name":"email","type":"stdio","command":"npx","args":["-y","@wraps.dev/mcp"],"env":{"WRAPS_API_KEY":"<YOUR_WRAPS_API_KEY>"}}'Install Amazon SES MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
],
"env": {
"WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
}
}
}
}Install Amazon SES MCP in Codex
$ codex mcp add email --env 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' -- npx -y @wraps.dev/mcpInstall Amazon SES MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.email] command = "npx" args = ["-y", "@wraps.dev/mcp"] [mcp_servers.email.env] WRAPS_API_KEY = "<YOUR_WRAPS_API_KEY>"
Install Amazon SES MCP in Gemini CLI
$ gemini mcp add -s user -e 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' email npx -- -y @wraps.dev/mcpInstall Amazon SES MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
],
"env": {
"WRAPS_API_KEY": "<YOUR_WRAPS_API_KEY>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @wraps.dev/mcp 0.11.1 in an isolated container with no network and no keys. It answered and listed 7 tools.
Amazon SES MCP tools 7
Read from the server with tools/listsend_emailActionSend 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_sendsRead-onlyList 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).
get_email_event_logRead-onlyGet the full delivery event log for a specific email by its messageId. Returns all SES events: Send, Delivery, Bounce, Complaint, Open, Click.
verify_domain_statusRead-onlyCheck 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.
list_suppressionsRead-onlyList 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).
get_setup_statusRead-onlyCheck 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.
estimate_costRead-onlyEstimate 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.
Configuration
WRAPS_API_KEYSecretWraps 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_PROFILEAWS profile to use. Credentials are read locally and never leave the machine.
AWS_REGIONRegion your Wraps stack is deployed in. Optional only if your active AWS profile supplies one — SES identities are per-region.
WRAPS_ALLOWED_RECIPIENTSComma-separated addresses the agent may send to. Restricts send_email when write mode is on.
WRAPS_ALLOWED_RECIPIENT_DOMAINSComma-separated domains the agent may send to. Matching is exact; list subdomains explicitly.
WRAPS_API_URLWraps API base URL. Defaults to https://api.wraps.dev; set it for a self-hosted control plane.
WRAPS_FROM_EMAILDefault from address for send_email. Must be a domain verified in your SES account.
WRAPS_HISTORY_TABLE_NAMEDynamoDB table holding email history. Defaults to wraps-email-history.
WRAPS_ORG_IDOrganization id to act in when using a `wraps auth login` session that belongs to several organizations.
WRAPS_WRITE_ENABLEDSet to true to enable the send_email tool. Read-only by default.
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@wraps.dev/mcp
MCP server for Amazon SES. Lets AI agents send email from your own AWS account, check domain verification and DKIM, look up the suppression list, and see whether the account is still in the SES sandbox.
Works with any SES account. Wraps adds send history and delivery events on top.
Runs locally via stdio. Your AWS credentials never leave your machine.
Prerequisites
- AWS credentials configured in your environment (a profile, SSO, or environment variables)
- An SES account in the region you point it at
- For
list_recent_sendsandget_email_event_logonly: the Wraps event pipeline, deployed withnpx @wraps.dev/cli email init - For the API-backed tools: a
WRAPS_API_KEY, or a session fromwraps auth login
Tools
| Tool | Description | Needs Wraps? | Write? |
|---|---|---|---|
send_email |
Send a transactional email via your SES account | No | Yes — requires WRAPS_WRITE_ENABLED=true |
verify_domain_status |
Check verification and DKIM status of a sending domain | No | No |
list_suppressions |
List addresses on your SES suppression list (paginated, with an explicit truncation notice), or check one address exactly with email |
No | No |
get_setup_status |
Check whether the account is in the SES sandbox, and get the next step toward a first send | No | No |
estimate_cost |
Estimate monthly Wraps + AWS cost for a send volume, including which SES pricing plan the account is on. No AWS credentials needed | No | No |
list_recent_sends |
List recent sends from your email history | Yes | No |
get_email_event_log |
Get the full delivery event log for a message (Send, Delivery, Bounce, Complaint, Open, Click) | Yes | No |
check_send_status |
Poll the outcome of a pending_approval send by approvalId (enforced mode only) |
Yes | No |
list_contacts |
List contacts in your Wraps organization, optionally filtered by email status, SMS status, preferred channel, or a search string on email or phone. | Yes (API key or wraps auth login) |
No |
get_contact |
Get one contact in full, including its topic subscriptions. | Yes (API key or wraps auth login) |
No |
create_contact |
Create one new contact. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
update_contact |
Change one existing contact. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
set_contact_topics |
REPLACE the full topic subscription list of one contact. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
delete_contact |
Permanently delete ONE contact by UUID, email, or externalId. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
validate_contact_emails |
Check up to 100 email addresses with SES Email Address Insights and return a deliverability verdict (HIGH, MEDIUM, LOW, or UNKNOWN) for each. | Yes (API key or wraps auth login) |
No |
import_contacts |
Import up to 10,000 contacts in one call, with created, updated, skipped and invalid counts and the reason for each rejected row. duplicateStrategy: "update" changes existing contacts and needs confirm: true. |
Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true (and confirm: true for update) |
export_contacts |
Export the contacts that match optional filters, newest first, up to 1,000 rows per call. truncated says when more matched. |
Yes (API key or wraps auth login) |
No |
get_account_health |
Get the SES sending health of the connected AWS accounts: status, last check time, quota, reputation and reasons, for all accounts or one by its Wraps id. | Yes (API key or wraps auth login) |
No |
email_check |
Check a domain's SPF, DKIM, DMARC, MX and blacklist setup and return a grade with the issues that cost points. The request is public and rate limited to 10 per minute per IP. | Yes (API key or wraps auth login); the request is sent without it |
No |
list_segments |
List the audience segments saved in this Wraps organization, with each segment's live member count. | Yes (API key or wraps auth login) |
No |
get_segment |
Get one audience segment by id, including its full filter condition and live member count. | Yes (API key or wraps auth login) |
No |
preview_segment |
Preview the audience an unsaved filter condition would reach, without saving a segment. | Yes (API key or wraps auth login) |
No |
create_segment |
Save a new audience segment from a filter condition. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
update_segment |
Change an existing audience segment: rename it, edit its description, replace its condition, or toggle trackMembership. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
delete_segment |
Permanently delete an audience segment. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_topics |
List the organization's subscription topics with live audience counts: subscriberCount (opted in), sendableCount (a broadcast would reach now) and pendingCount (waiting on double opt-in). | Yes (API key or wraps auth login) |
No |
get_topic |
Get one subscription topic by id, with its audience counts (subscriberCount, sendableCount, pendingCount) and its creator. | Yes (API key or wraps auth login) |
No |
list_topic_subscribers |
List the contacts subscribed to one topic, filtered by status (subscribed, pending for double opt-in not yet confirmed, or unsubscribed). | Yes (API key or wraps auth login) |
No |
create_topic |
Create a subscription topic that contacts can subscribe to and broadcasts can target. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
update_topic |
Change a subscription topic's name, slug, description, public flag or double opt-in setting. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
delete_topic |
Permanently delete a subscription topic and every subscription to it. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_templates |
List the Wraps email and SMS templates in your organization. | Yes (API key or wraps auth login) |
No |
get_template |
Get one Wraps template by id: its metadata, status, variables, and by default its React Email source, compiled HTML, and compiled text. | Yes (API key or wraps auth login) |
No |
create_template |
Create a new Wraps email or SMS template as a DRAFT. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
update_template |
Change an existing Wraps template. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
duplicate_template |
Copy an existing Wraps template to start a variant. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
publish_template |
Publish a Wraps template to SES, so sends and workflows that use it get this content. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
delete_template |
Permanently delete up to 100 Wraps templates with their versions, and their published SES copies where no other template uses the same SES name. Refused with 409 (nothing deleted) while a draft, scheduled, queued or processing broadcast, or an enabled workflow, uses one. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_broadcasts |
List broadcasts (email or SMS batch sends) for your organization, with their status and delivery counts. | Yes (API key or wraps auth login) |
No |
get_broadcast |
Get the status and delivery counts of ONE broadcast by id. | Yes (API key or wraps auth login) |
No |
list_broadcast_recipients |
List the per-recipient outcome of one broadcast: who was sent to, and whether each send was delivered, bounced, suppressed or failed, with the error reason. | Yes (API key or wraps auth login) |
No |
get_broadcast_clicks |
Get the link-click breakdown for ONE broadcast: which URLs were clicked and how often, plus the unsubscribe click count. | Yes (API key or wraps auth login) |
No |
create_broadcast |
Create a NEW broadcast as a draft. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
update_broadcast |
Edit a DRAFT or a SCHEDULED broadcast: its content, sender, audience, template, AWS account or send time. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
duplicate_broadcast |
Copy an existing broadcast into a NEW draft, whatever the status of the original. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
send_broadcast |
Send a DRAFT broadcast to its audience, now or at scheduledFor. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
resume_broadcast |
Resume an email broadcast that stopped part-way, from the last chunk it finished, so recipients who were not yet sent to get the message. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
cancel_broadcast |
Cancel a broadcast that is scheduled, queued or processing, so the messages that have not gone out yet are not sent. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_events |
List custom events tracked for this Wraps organization, newest first, optionally filtered by event name, contact, text search, or date range. | Yes (API key or wraps auth login) |
No |
get_event |
Get one custom event by id: its name, properties, time, and the contact it belongs to. | Yes (API key or wraps auth login) |
No |
get_event_analytics |
Get custom-event totals for this organization over the last 7 or 30 days: events in the period, active contacts, average events per contact, a zero-filled daily series, and the top event names. | Yes (API key or wraps auth login) |
No |
list_event_names |
List every distinct custom event name recorded for this Wraps organization, sorted. | Yes (API key or wraps auth login) |
No |
track_event |
Record a custom event for one contact. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
remove_suppression |
Remove one address from the SES account-level suppression list of one AWS account, so Wraps sends to it again. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
add_suppression |
Add one or more addresses to the SES account-level suppression list of one AWS account, so Wraps stops sending to them. Up to 100 per call; undo one at a time with remove_suppression. |
Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_workflows |
List the email and SMS automation workflows in your Wraps organization, newest first, with status and execution counts. | Yes (API key or wraps auth login) |
No |
get_workflow |
Get one workflow by id, including its trigger config, steps and transitions, so you can see what it does before triggering it or changing its schedule. | Yes (API key or wraps auth login) |
No |
list_workflow_executions |
List the executions of one workflow (one run per contact), newest first, each with its contact and status. | Yes (API key or wraps auth login) |
No |
get_workflow_execution |
Get one workflow execution by id, with its step trace (every step it reached and that step status), its contact, the workflow name and per-step engagement. | Yes (API key or wraps auth login) |
No |
enable_workflow_schedule |
Turn on the recurring schedule of a schedule-triggered workflow by creating its next one-time run from a cron expression and timezone. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
disable_workflow_schedule |
Turn off the recurring schedule of a schedule-triggered workflow by deleting its pending scheduled run. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
trigger_workflow |
Start one run of an API-triggered workflow for one contact, so the workflow steps begin for that contact now. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
retry_workflow_execution |
Retry a failed workflow execution from the step where it failed. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
cancel_workflow_execution |
Cancel a workflow execution that is still running (pending, active, paused or waiting), so no further steps run for that contact and its scheduled steps are removed. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_agent_approvals |
List the approval queue for agents: the sends that an agent asked to make and that were held for a human decision. | Yes (API key or wraps auth login) |
No |
approve_agent_approval |
Approve one send that an agent asked to make and that was held for a human decision, so Wraps sends it now. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
reject_agent_approval |
Reject one send that an agent asked to make and that was held for a human decision, so it is never delivered. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
list_agents |
List the leashed agents in this organization: each one's address, send policy (caps and allowlists) and whether it is ACTIVE or KILLED. | Yes (API key or wraps auth login) |
No |
create_agent |
Create a leashed agent: a named sender with its own email address and send policy. Recorded in Wraps only; its AWS resources are deployed with the CLI. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
kill_agent |
Kill one leashed agent so it can no longer send. Irreversible; a kill that does not reach the enforcer is reported as incomplete. Not registered in enforced mode. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
set_agent_policy |
Replace one leashed agent's send policy (hourly and daily caps and recipient allowlists) in full. Overwrites the previous policy. Not registered in enforced mode. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
get_email_metrics |
Get aggregate email sending metrics for this organization over a time window: sent, delivered, bounced (split into permanent, transient and undetermined), complained, suppressed, opened, clicked, failed, and an estimated costUsd. | Yes (API key or wraps auth login) |
No |
list_inbound_emails |
List one page of parsed inbound emails that the customer's SES inbound bucket received, across the organization's connected AWS accounts. Each entry includes envelope recipients (when recorded). | Yes (API key or wraps auth login) |
No |
get_inbound_email |
Get one parsed inbound email from the customer's SES inbound bucket by emailId, with its from/to/cc, subject, date, headers, text body, HTML body, attachment metadata and envelope recipients (when recorded). | Yes (API key or wraps auth login) |
No |
list_brand_kits |
List the organization's brand kits: name, logo, colors, fonts, button style, company details and social links, with isDefault marking the one default kit. | Yes (API key or wraps auth login) |
No |
get_brand_kit |
Get one brand kit by id: logo, colors, fonts, button style, company details, social links, and isDefault. | Yes (API key or wraps auth login) |
No |
create_brand_kit |
Create a brand kit: a name, logo, colors, fonts, button style, company details and social links that email templates can use. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
update_brand_kit |
Change one or more fields of a brand kit: name, logo, colors, fonts, button style, company details, social links. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
set_default_brand_kit |
Make one brand kit the default for the organization. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true |
delete_brand_kit |
Delete a brand kit permanently. | Yes (API key or wraps auth login) |
Yes — requires WRAPS_WRITE_ENABLED=true and confirm: true |
The API-backed rows ("Needs Wraps?" = Yes) need a Wraps API credential. See Wraps API tools.
Setup
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"wraps": {
"command": "npx",
"args": ["-y", "@wraps.dev/mcp"],
"env": {
"AWS_REGION": "us-east-1",
"AWS_PROFILE": "your-aws-profile"
}
}
}
}
Claude Code
Add to .mcp.json in your project root:
{
"mcpServers": {
"wraps": {
"command": "npx",
"args": ["-y", "@wraps.dev/mcp"],
"env": {
"AWS_REGION": "us-east-1"
}
}
}
}
Set AWS_REGION to the region your Wraps stack is deployed in — SES identities are per-region, and a domain verified in another region reads as "not found". Claude Code inherits your shell's AWS environment, so you can drop the env block entirely if AWS_REGION (or a region in your active AWS profile) is already set there; the server fails at startup if neither supplies one.
Configuration
All configuration is via environment variables.
| Variable | Required | Default | Description |
|---|---|---|---|
AWS_REGION |
Yes* | — | AWS region where your Wraps stack is deployed. *Required unless your active AWS profile (~/.aws/config) supplies a region — the server resolves AWS_REGION, then AWS_DEFAULT_REGION, then the profile, and errors at startup if none of them do. |
WRAPS_HISTORY_TABLE_NAME |
No | wraps-email-history |
DynamoDB table name for email history |
WRAPS_ACCOUNT_ID |
No | auto-detected via STS | Your AWS account ID (skip STS call if set) |
WRAPS_WRITE_ENABLED |
No | false |
Set to true to enable send_email and every write or destructive API-backed tool |
WRAPS_FROM_EMAIL |
No | — | Default from address for send_email |
WRAPS_API_KEY |
No | — | Wraps API key (wraps_...) for the API-backed tools. Without it, the session from wraps auth login is used |
WRAPS_API_URL |
No | https://api.wraps.dev |
Wraps API base URL. Set it for a self-hosted control plane |
WRAPS_ORG_ID |
No | — | Organization to act in when the session belongs to several. Sent as x-organization-id |
Wraps API tools
The tools marked "Needs Wraps? Yes (API key or wraps auth login)" call the Wraps API for your organization. They register at startup only when a credential is present. The server uses the first of these that it finds:
WRAPS_API_KEY, awraps_...key.- The unexpired session stored by
wraps auth login(orwraps selfhost loginfor a self-hosted instance).
With neither, only the AWS tools register. An expired or revoked credential does not stop startup; the call returns a tool error that names the fix.
Write tools need WRAPS_WRITE_ENABLED=true. Destructive tools also need confirm: true in the call, so set it only after the user has confirmed the change. When WRAPS_AGENT_ID is set (enforced mode), approve_agent_approval, reject_agent_approval, create_agent, kill_agent and set_agent_policy are not registered. list_agents stays registered.
{
"mcpServers": {
"wraps": {
"command": "npx",
"args": ["-y", "@wraps.dev/mcp"],
"env": {
"AWS_REGION": "us-east-1",
"WRAPS_API_KEY": "wraps_..."
}
}
}
}
Write Mode
send_email and the other write tools are disabled by default. Set WRAPS_WRITE_ENABLED=true to enable them. The from address must be a domain verified in your SES account.
{
"mcpServers": {
"wraps": {
"command": "npx",
"args": ["-y", "@wraps.dev/mcp"],
"env": {
"AWS_REGION": "us-east-1",
"WRAPS_WRITE_ENABLED": "true",
"WRAPS_FROM_EMAIL": "you@yourdomain.com"
}
}
}
}
Send guardrails
When write mode is enabled, the send_email tool can reach any SES-verified address by default. Use these env vars to restrict the agent's sending scope:
| Variable | Default | Description |
|---|---|---|
WRAPS_ALLOWED_RECIPIENTS |
— (no restriction) | Comma-separated exact addresses the agent may send to. If set, any address not in this list (or WRAPS_ALLOWED_RECIPIENT_DOMAINS) is rejected. |
WRAPS_ALLOWED_RECIPIENT_DOMAINS |
— (no restriction) | Comma-separated domains (e.g. company.com,partner.org) the agent may send to. Combined with WRAPS_ALLOWED_RECIPIENTS; a recipient is allowed if it matches either list. Matching is exact: example.com allows user@example.com but NOT subdomains like user@mail.example.com — list each subdomain explicitly. |
WRAPS_MAX_RECIPIENTS |
50 |
Maximum number of recipients per send_email call. |
WRAPS_ALLOW_FROM_OVERRIDE |
false |
Set to true to let the agent supply a from address that differs from WRAPS_FROM_EMAIL. When false (default), the caller-supplied from is rejected if it does not match the configured address. |
Note: Running with
WRAPS_WRITE_ENABLED=trueand no allowlist gives the agent unrestricted send capability to any address in your SES account.
Asking for missing input (elicitation)
If your MCP client supports elicitation, send_email asks you for input it is missing instead of failing. It never asks you to confirm an ordinary send, and it asks only after the write, recipient-count and allowlist checks above have passed.
- No sender. If the call has no
fromandWRAPS_FROM_EMAILis not set, the client prompts for the sender address. - SES sandbox. If SES rejects the recipient because the account is in the sandbox, the client offers to send the message to the AWS mailbox simulator (
success@simulator.amazonses.com) instead, to prove sending works. This happens once, and the simulator address must pass your recipient allowlist. The result says the message went to the simulator and not to the original recipient.
If you decline or cancel, or the client does not support elicitation, you get the same error as before. No setting is needed. Enforced mode does not use elicitation; its approvals stay with the operator.
Amazon SES MCP questions
How do I add Amazon SES MCP to Claude Code?
Run claude mcp add --env 'WRAPS_API_KEY=<YOUR_WRAPS_API_KEY>' email -- npx -y @wraps.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Amazon SES MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Amazon SES MCP provide?
It exposes 7 tools, including send_email, list_recent_sends, get_email_event_log, verify_domain_status, list_suppressions.
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.