Wraps MCP Server
dev.wraps/docs
Search Wraps docs and estimate AWS SES costs for your email infrastructure.
What is the Wraps MCP server?
The Wraps MCP server provides tools to search Wraps documentation and estimate AWS SES email sending costs. It enables AI agents to quickly reference Wraps guides, SDK/CLI reference, and calculate pricing for email deployments to your AWS account.
This server gives Claude, Cursor, and other AI agents access to Wraps documentation and cost estimation tools. Use it to get instant answers about deploying email infrastructure to AWS, understand SDK/CLI usage, and estimate SES pricing for your email volume.
How to install Wraps
Copy-paste configuration for popular MCP clients.
Tools & capabilities
Tools this server exposes to the agent.
search_docs— Search the Wraps documentation including quickstarts, SDK reference, CLI reference, and guides.estimate_ses_costs— Estimate AWS SES costs based on email volume and sending patterns.check_setup_status— Check the setup status of Wraps email infrastructure in your AWS account.read_event_logs— Read and retrieve email event logs (bounces, opens, clicks, deliveries) from your Wraps deployment.
Use cases
- Get instant answers about Wraps documentation while building email infrastructure
- Estimate AWS SES costs before deploying email to production
- Check the status of your Wraps email setup and infrastructure health
- Review email delivery events and troubleshoot bounces or failures
- Reference SDK and CLI commands while developing with Wraps
Wraps MCP server FAQ
It's a Model Context Protocol server that gives AI agents like Claude and Cursor access to Wraps documentation and tools for managing email infrastructure on AWS, including cost estimation and event log retrieval.
Wraps itself is open-source (AGPL-3.0), but you pay AWS directly for SES, Lambda, DynamoDB, and other AWS resources used. There's no Wraps markup—you get AWS pricing directly.
Add the remote MCP server at https://wraps.dev/mcp to your Cursor or Claude configuration. Alternatively, run locally with `npx -y @wraps.dev/mcp`.
No. The MCP server is public and read-only. It accesses public documentation and cost estimation. AWS credentials are only needed when you deploy email infrastructure with the Wraps CLI.
SES (with domain verification and DKIM/SPF/DMARC), EventBridge + SQS for event tracking, DynamoDB for email history, Lambda for processing, and IAM roles—all namespaced under `wraps-` and tagged for easy management.
Yes. Wraps provides a Python SDK (`wraps-email`), CDK construct, Pulumi component, and a platform API client for other languages.
README (reference)
Source of truth, from the repository.
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 withnpx -y @wraps.dev/mcpfor 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
| Service | CLI | SDK |
|---|---|---|
| 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
| Resource | Link |
|---|---|
| Quickstart | wraps.dev/docs/quickstart |
| CLI Reference | wraps.dev/docs/cli-reference |
| SDK Reference | wraps.dev/docs/sdk-reference |
| Python SDK Reference | wraps.dev/docs/python-sdk-reference |
| MCP Reference | wraps.dev/docs/mcp-reference |
| Guides | wraps.dev/docs/guides |
| Infrastructure | wraps.dev/docs/infrastructure |
| Complete docs for LLMs | wraps.dev/llms-full.txt |
Community
- GitHub Issues — Bug reports and feature requests
- GitHub Discussions — Questions and ideas
- Contributing — Development setup and guidelines
License
AGPL-3.0 — see LICENSE for details. Enterprise features under commercial license. See wraps.dev for more information.
Related MCP servers

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

XFMS — Model Source
Pick the right LLM for any task. Ranked shortlist with rationale across 8 evaluators.
Read-only Solana and Robinhood Chain tools: wallet recovery, token safety, unlocks, upgrades, fees.

dev.yafl/mcp
Agent-first E2EE file transfer over MCP: move files between machines in one tool call, gone in 24h.
deploy the software your AI builds you
Trust Layer for AI work. Give your AI hands. Every run returns a verifiable receipt. No key needed.
View repository →