dev.wraps/email
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
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).
@wraps.dev/mcpclaude mcp add email -e 'AWS_REGION=<AWS_REGION>' -e 'AWS_PROFILE=<AWS_PROFILE>' -e 'WRAPS_WRITE_ENABLED=<WRAPS_WRITE_ENABLED>' -e 'WRAPS_FROM_EMAIL=<WRAPS_FROM_EMAIL>' -e 'WRAPS_ALLOWED_RECIPIENTS=<WRAPS_ALLOWED_RECIPIENTS>' -e 'WRAPS_ALLOWED_RECIPIENT_DOMAINS=<WRAPS_ALLOWED_RECIPIENT_DOMAINS>' -e 'WRAPS_HISTORY_TABLE_NAME=<WRAPS_HISTORY_TABLE_NAME>' -- npx -y @wraps.dev/mcp@0.9.0{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp@0.9.0"
],
"env": {
"AWS_REGION": "<AWS_REGION>",
"AWS_PROFILE": "<AWS_PROFILE>",
"WRAPS_WRITE_ENABLED": "<WRAPS_WRITE_ENABLED>",
"WRAPS_FROM_EMAIL": "<WRAPS_FROM_EMAIL>",
"WRAPS_ALLOWED_RECIPIENTS": "<WRAPS_ALLOWED_RECIPIENTS>",
"WRAPS_ALLOWED_RECIPIENT_DOMAINS": "<WRAPS_ALLOWED_RECIPIENT_DOMAINS>",
"WRAPS_HISTORY_TABLE_NAME": "<WRAPS_HISTORY_TABLE_NAME>"
}
}
}
}Environment variables
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.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
TypeScript SDKs and an MCP server for AWS services. Your infrastructure, great DX.
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/emailimport { 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/smsimport { 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/clientimport { 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.
@wraps.dev/mcp — MCP server for Amazon SES
A Model Context Protocol server that lets AI agents send email from your own AWS account and inspect it. It runs locally over stdio, built on the official MCP TypeScript SDK, and reads AWS credentials from your environment.
{
"mcpServers": {
"wraps": {
"command": "npx",
"args": ["-y", "@wraps.dev/mcp"],
"env": { "AWS_REGION": "us-east-1", "AWS_PROFILE": "your-aws-profile" }
}
}
}Tools: send_email (off unless WRAPS_WRITE_ENABLED=true), verify_domain_status, list_suppressions, get_setup_status, and estimate_cost work on any SES account. list_recent_sends and get_email_event_log read send history from a Wraps deploy. Also runs from the Dockerfile at the repo root: docker build -t wraps-mcp . && docker run -i --rm -e AWS_REGION wraps-mcp. MCP docs →
Documentation
| Resource | Link |
|---|---|
| Quickstart | wraps.dev/docs/quickstart |
| SDK Reference | wraps.dev/docs/sdk-reference |
| SMS Docs | wraps.dev/docs/sms-sdk-reference |
| MCP Server | wraps.dev/docs/mcp-reference |
| CLI (deploy infra) | wraps.dev/docs/cli-reference |
Community
- GitHub Issues — Bug reports and feature requests
- GitHub Discussions — Questions and ideas
- Contributing — Development setup and guidelines
License
MIT — see LICENSE for details.
Frequently asked questions
What is dev.wraps/email?
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
How do I install dev.wraps/email?
It runs on your machine. In Claude Code: claude mcp add email -e 'AWS_REGION=<AWS_REGION>' -e 'AWS_PROFILE=<AWS_PROFILE>' -e 'WRAPS_WRITE_ENABLED=<WRAPS_WRITE_ENABLED>' -e 'WRAPS_FROM_EMAIL=<WRAPS_FROM_EMAIL>' -e 'WRAPS_ALLOWED_RECIPIENTS=<WRAPS_ALLOWED_RECIPIENTS>' -e 'WRAPS_ALLOWED_RECIPIENT_DOMAINS=<WRAPS_ALLOWED_RECIPIENT_DOMAINS>' -e 'WRAPS_HISTORY_TABLE_NAME=<WRAPS_HISTORY_TABLE_NAME>' -- npx -y @wraps.dev/mcp@0.9.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does dev.wraps/email 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 dev.wraps/email open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains dev.wraps/email?
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.