Skip to content
MCP server

Email

Send email and check SES domains, suppressions and sandbox status from your AWS account

Runs locallyStatus and history
Install
Pricing
Freemium
Platforms
CLI, self-hosted, API
Runs
Locally
Version
0.11.1
Listing updated
3 days ago

About Email

Email is a freemium MCP server for communication. It runs locally on your machine and is started by your AI client.

Credentials come from your local AWS profile or environment and never leave the machine. Without extra setup the tools are read-only: verify_domain_status checks a domain's verification and DKIM, list_suppressions pages through the suppression list or checks one address, get_setup_status reports whether the account is still in the SES sandbox, and estimate_cost projects monthly Wraps and AWS cost for a send volume.

Sending is off by default. Setting WRAPS_WRITE_ENABLED=true enables send_email, and WRAPS_ALLOWED_RECIPIENTS or WRAPS_ALLOWED_RECIPIENT_DOMAINS can restrict where an agent may send, with domains matched exactly. The sender must be a domain verified in SES.

Send history and delivery events (send, delivery, bounce, complaint, open, click) need the Wraps event pipeline deployed in your account. A WRAPS_API_KEY or an auth login session additionally registers tools for contacts, segments, topics, templates, broadcasts, workflows, approvals and more, and an approval flow can hold sends as pending_approval.

Install

Run in a terminal

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

Add to claude_desktop_config.json

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

Add to ~/.cursor/mcp.json

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

Add to .vscode/mcp.json

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

Add to ~/.codeium/windsurf/mcp_config.json

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

Add to your client's MCP settings (most use this shape)

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

Configuration

  • AWS_REGIONRegion your Wraps stack is deployed in. Optional only if your active AWS profile supplies one — SES identities are per-region.
  • AWS_PROFILEAWS profile to use. Credentials are read locally and never leave the machine.
  • WRAPS_WRITE_ENABLEDSet to true to enable the send_email tool. Read-only by default.
  • WRAPS_FROM_EMAILDefault from address for send_email. Must be a domain verified in your SES account.
  • 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_HISTORY_TABLE_NAMEDynamoDB table holding email history. Defaults to wraps-email-history.
  • WRAPS_API_KEYWraps 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.
  • WRAPS_API_URLWraps API base URL. Defaults to https://api.wraps.dev; set it for a self-hosted control plane.
  • WRAPS_ORG_IDOrganization id to act in when using a `wraps auth login` session that belongs to several organizations.

Tools this server provides (8)

Taken from the project documentation; the running server may differ.

send_email
Send a transactional email via your SES account; needs write mode
verify_domain_status
Check verification and DKIM status of a sending domain
list_suppressions
List suppressed addresses or check one address
get_setup_status
Check SES sandbox status and the next step toward a first send
estimate_cost
Estimate monthly Wraps and AWS cost for a send volume
list_recent_sends
List recent sends from email history
get_email_event_log
Delivery event log for a message
check_send_status
Poll the outcome of a pending_approval send

What it does

Read-only by default
Write mode must be enabled explicitly.
Recipient allowlists
Limit sends to listed addresses or exact domains.
Domain and DKIM checks
Verify a sending domain's status.
Suppression lookup
List suppressed addresses or test one.
Sandbox status
See whether SES is still in sandbox and the next step.
Delivery event log
Get send, delivery, bounce, complaint, open and click events per message.

Good for

  • Ask why a domain is not yet verified for sending
  • Check whether an address is on the suppression list
  • Send a transactional email from an agent with an allowlist
  • Estimate monthly cost for a planned send volume
  • Trace what happened to a specific message

Pricing

Freemium

Wraps is free to start; AWS bills sending at $0.10 per 1K (à la carte) or $0.16 per 1K (Essentials)

Prices change. Check wraps.dev before you buy.

Email FAQ

Can an agent send mail by default?

No. send_email needs WRAPS_WRITE_ENABLED=true.

Do I need a Wraps account?

Not for the core SES tools. Event history and the platform tools need the Wraps pipeline or an API key.

Do my AWS keys leave my machine?

The README says credentials are read locally and never leave the machine.

What does Wraps cost?

The site says free to start, with sending billed by AWS at $0.10 per 1K on à la carte or $0.16 per 1K on Essentials.

Is Email free?

Email has a free plan, with paid plans for more usage or features.

How do I add Email to Claude Code?

Run this command in your terminal: claude mcp add email --env WRAPS_API_KEY='<WRAPS_API_KEY>' -- npx -y @wraps.dev/mcp

What are the best alternatives to Email?

The closest alternatives to Email are BoardAgent, Callout, nicemails, SOMMON Office and PostBaton.

Alternatives to Email

  1. BoardAgent

    MCP server

    Remote MCP server for a message board where only AI agents post, reply and vote

    • 27 tools
    • Remote
    • Free
    • Community directories
  2. Callout

    MCP server

    Let an AI agent place real phone calls in Japanese or English and read the transcript

    • 5 tools
    • Remote
    • Freemium
    • Communication
  3. nicemails

    MCP server

    Give each AI agent its own real mailbox to read, search and send email with your approval

    • 8 tools
    • Remote
    • Freemium
    • Communication
  4. SOMMON Office

    MCP server

    Send real paper letters via Deutsche Post from an AI assistant, to 218 countries

    Not checked yet
    • 14 tools
    • Remote
    • Paid
    • Communication
  5. PostBaton

    MCP server

    Schedule, edit and cancel social posts across networks from an AI assistant or REST API

    Not checked yet
    • Remote
    • Freemium
    • Marketing and SEO
  6. MeetBetr

    MCP server

    Find when friends are free and send them a plan after you confirm it

    • Remote
    • Free
    • Productivity