What it is

Wraps is a code-first email platform that deploys its infrastructure into your own AWS account. It lives in the AWS and TypeScript ecosystem, and it ships as a command line tool, a set of SDKs, and an agent-facing MCP server. The core idea is that sending email does not require handing your data or your billing to a third party: one CLI command provisions the resources, and the application talks to them through a typed client. SMS through AWS End User Messaging, and CDN delivery over S3 and CloudFront, follow the same pattern.

The concrete problem it solves is the gap between raw AWS primitives and a usable sending stack. AWS SES requires domain verification, DKIM, SPF and DMARC configuration, plus event plumbing for bounces, opens, clicks and deliveries, plus storage for that event history. Wraps reduces that to npx @wraps.dev/cli email init, which creates SES configuration, EventBridge and SQS event tracking, a DynamoDB event history table with configurable retention, Lambda event processing and webhook handling, and least-privilege IAM roles with OIDC support for Vercel and AWS native identities. All resources are namespaced under wraps- and tagged ManagedBy: wraps-cli. The stated consequence is that the data never leaves your cloud, and the email keeps working if the vendor disappears.

Key capabilities

• Deploys SES domain verification, DKIM, SPF and DMARC records through a single CLI command.
• Provisions EventBridge and SQS for real-time event tracking of bounces, opens, clicks and deliveries.
• Creates a DynamoDB table for email event history with configurable retention.
• Generates Lambda functions for event processing and webhook handling.
• Creates least-privilege IAM roles with OIDC support for Vercel and AWS native identity providers.
• Provides a TypeScript SDK, @wraps.dev/email, with a WrapsEmail class and a send method returning a messageId.
• Offers an MCP server hosted at https://wraps.dev/mcp or run locally with npx -y @wraps.dev/mcp for tools that send email, check setup status and read event logs.

Who uses it and how

• Application developers who want to send transactional email from TypeScript without adopting a hosted email API vendor.
• Teams that need bounce, open, click and delivery tracking wired into their own AWS account rather than a vendor dashboard.
• SMS and CDN consumers, who use wraps sms init with @wraps.dev/sms and wraps cdn init for S3 and

# Deploy email infrastructure to your AWS account
npx @wraps.dev/cli email init

# Install the SDK
pnpm add @wraps.dev/email

import { WrapsEmail } from '@wraps.dev/email';

const email = new WrapsEmail();

const { messageId } = await email.send({
  from: '[email protected]',
  to: '[email protected]',
  subject: 'Welcome!',
  html: '<h1>Hello from Wraps!</h1>',
});

console.log('Sent:', messageId);