Back to Directory/Cloud Providers

dev.wraps/email

Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.

Cloud ProvidersTypeScriptv0.8.2

AI agents: start with AGENTS.md — which package to reach for, auth, the minimal correct call for each, and the sharp edges. For the full docs in one file, fetch wraps.dev/llms-full.txt, or wraps.dev/llms.txt for an agent-oriented index.

Packages

@wraps.dev/email — AWS SES

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>',
});

React.email support, template management, bulk sending, inbox reading, event history, and suppression lists. SDK docs →

@wraps.dev/sms — AWS End User Messaging

pnpm add @wraps.dev/sms
import { WrapsSMS } from '@wraps.dev/sms';

const sms = new WrapsSMS();

await sms.send({
  to: '+14155551234',
  message: 'Your verification code is 123456',
});

Batch sending, opt-out management, and E.164 validation. SMS docs →

@wraps.dev/client — Wraps Platform API

pnpm add @wraps.dev/client
import { createPlatformClient } from '@wraps.dev/client';

const client = createPlatformClient({ apiKey: 'your-api-key' });

const { data } = await client.GET('/v1/contacts/', {
  params: { query: { page: '1', pageSize: '10' } },
});

Auto-generated types from OpenAPI, workflow definitions, and brand kit configuration.

Documentation

ResourceLink
Quickstartwraps.dev/docs/quickstart
SDK Referencewraps.dev/docs/sdk-reference
SMS Docswraps.dev/docs/sms-sdk-reference
CLI (deploy infra)wraps.dev/docs/cli-reference

Community

License

MIT — see LICENSE for details.

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y @wraps.dev/mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

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

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

@wraps.dev/mcpnpm

Compatible MCP Clients

dev.wraps/email works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More