Wraps MCP
Wraps MCP server: send email through your own AWS, check setup status and read the delivery event log from an agent
- 67 ★ on the repository
- Last commit
Broad access
Why this level
- Sends email from your domain using AWS credentials
- Reads the delivery event log containing recipient addresses
Install
- Works in
Manual install
npx -y @wraps.dev/mcpLocal run; hosted address: https://wraps.dev/mcp.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Sends email from your domain using AWS credentials
- Reads the delivery event log containing recipient addresses
This is third-party code. Review the repository files before installing.
What it does
Wraps deploys email infrastructure into the user own AWS account with one command: SES with DKIM, SPF and DMARC, event queues, message history storage and processing functions. The MCP server from this repository gives an agent tools to send email, check setup status and read the event log. The server runs hosted at `https://wraps.dev/mcp` or locally through `npx -y @wraps.dev/mcp`. Agent docs are bundled in llms.txt and llms-full.txt files, and Claude Code skills are served from wraps.dev. The same repository holds the CLI, a TypeScript SDK and CDK and Pulumi components.
Who it is for. Developers who send email through AWS SES and want to manage sending and delivery troubleshooting from an agent.
Good fit when
- The agent checks that domain, DKIM and events are set up correctly after install
- A test message is sent from the agent while debugging an app
- The event log is read to find bounces and complaints
- The team wants to pay AWS directly, without an email service markup
- You want a ready path from an empty AWS account to the first sent message
Not a fit when
- You have no AWS account, the infrastructure deploys only there
- Sending already goes through another email service and you do not plan to move
- Sending email must not be delegated to an agent
Example request
Check that email on my domain is set up and send a test message to my addressMCP
- Transport
- stdio, http
- Authentication
- API key
Limitations
Deployment requires Node.js 22 or newer and configured AWS credentials; resources are created in your account and billed at AWS rates. Variables and permissions of the MCP server itself are in the reference at wraps.dev/docs/mcp-reference, the README does not list them. A new AWS account may sit in the SES sandbox with a sending limit, lifted by a request to AWS. The repository license is marked NOASSERTION, so check its terms before using it in a product.
How to disable. Remove the server entry from the client configuration. Deployed AWS resources prefixed `wraps-` are removed by the Wraps CLI.
FAQ
Where does the Wraps infrastructure run?
In your AWS account: SES, EventBridge, SQS, DynamoDB, Lambda and IAM roles, all resources prefixed `wraps-`.
How do I deploy email?
With `npx @wraps.dev/cli email init`, which needs Node.js 22 and AWS credentials.
Are SMS and CDN covered?
Yes, `wraps sms init` and `wraps cdn init` set up SMS on AWS End User Messaging and a CDN on S3 with CloudFront.
What does the MCP server do?
It sends email, checks setup status and reads the event log.
Are there agent docs?
Yes, `wraps.dev/llms.txt` and `wraps.dev/llms-full.txt`, and Claude Code skills live at wraps.dev/.well-known/skills.
Discussion
No questions or reviews yet.
Related
MCP serversAWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
Cloudflare MCP servers
Cloudflare MCP Server
A set of remote Cloudflare MCP servers: documentation, Workers, logs, Radar, browser, DNS and other account services
MCPM
mcpm
A package manager and registry for MCP on all platforms and clients: finds, adds and configures MCP servers, remembers the source and updates
Amazon SES observability MCP server: an agent searches email events, inspects bounces and pulls delivery stats
An agent searches AWS CloudWatch logs, summarizes activity and correlates events across services.
A self-hosted gateway routes internal MCP tools, authenticates users and records requests for later review.
README in short
The README covers the quick start, the AWS resources deployed, packages for SMS, CDN, Python, CDK and Pulumi, and a section for agents with llms.txt files and the MCP server address.