Wraps

Official registry Search and web

Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http wraps 'https://wraps.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "wraps": {
            "type": "http",
            "url": "https://wraps.dev/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Quick Start
  2. For AI Agents
  3. Why Wraps?
  4. What Gets Deployed
  5. Also Available
  6. Documentation
  7. Community
  8. License

Deploy email infrastructure to your AWS account in under 2 minutes.


Quick Start

Prerequisites: Node.js 22+, AWS credentials configured

# 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: 'hello@yourapp.com',
  to: 'user@example.com',
  subject: 'Welcome!',
  html: '<h1>Hello from Wraps!</h1>',
});

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

For AI Agents

Using Claude Code, Cursor, or another AI assistant? Point it at:

  • wraps.dev/llms-full.txt — the complete Wraps documentation in one file (quickstarts, SDK reference, CLI reference, guides)
  • wraps.dev/llms.txt — agent-oriented index: when to use Wraps, quick command reference, links to everything
  • Claude Code skills — installable from wraps.dev/.well-known/skills/
  • 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 (reference)

Why Wraps?

  • You own it — Infrastructure deploys to your AWS account. Data never leaves your cloud. If we disappeared tomorrow, your email keeps working.
  • 2-minute setup — One CLI command. No AWS console spelunking. No 1000-word sandbox approval essays.
  • AWS pricing — Pay AWS directly for sending. No middleman markup. Scale affordably.
  • Real DX — TypeScript SDK, visual templates, real-time analytics, interactive dashboard.

What Gets Deployed

One command creates all of this in your AWS account:

  • SES — Domain verification, DKIM, SPF, DMARC
  • EventBridge + SQS — Real-time event tracking (bounces, opens, clicks, deliveries)
  • DynamoDB — Email event history with configurable retention
  • Lambda — Event processing and webhook handling
  • IAM — Least-privilege roles with OIDC support (Vercel, AWS native)

All resources are namespaced under wraps- (most as wraps-email-*) and tagged ManagedBy: wraps-cli.

Also Available

ServiceCLISDK
SMS (AWS End User Messaging)wraps sms init@wraps.dev/sms
CDN (S3 + CloudFront)wraps cdn init—
Email (Python)—wraps-email
Platform API client—@wraps.dev/client
MCP server—@wraps.dev/mcp
CDK construct—@wraps.dev/cdk
Pulumi component—@wraps.dev/pulumi

Documentation

Community

License

AGPL-3.0 — see LICENSE for details. Enterprise features under commercial license. See wraps.dev for more information.

Frequently asked questions

What is Wraps?

Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.

How do I install Wraps?

It runs as a remote server. In Claude Code: claude mcp add --transport http wraps 'https://wraps.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Wraps need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Wraps open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Wraps?

It is published by wraps-team. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.