Email runs on your own machine — the client starts it, so there is no endpoint to ping. 415 installs a week from npm. Last commit 2 Nov 2026.
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
What the code does
We read the source, 22 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
COPY package.json pnpm-lock.yaml pnpm-workspace.yaml .npmrc ./
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add email -- npx -y @wraps.dev/mcp{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
]
}
}
}[mcp_servers.email]
command = "npx"
args = ["-y", "@wraps.dev/mcp"]{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
]
}
}
}{
"servers": {
"email": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp"
]
}
}
}Optional settings from the registry entry, left out of the block above:
AWS_REGION (Region your Wraps stack is deployed in. Optional only if your active AWS profile supplies one — SES identities are per-region), AWS_PROFILE (AWS profile to use. Credentials are read locally and never leave the machine), WRAPS_WRITE_ENABLED (Set to true to enable the send_email tool. Read-only by default), WRAPS_FROM_EMAIL (Default from address for send_email. Must be a domain verified in your SES account), WRAPS_ALLOWED_RECIPIENTS (Comma-separated addresses the agent may send to. Restricts send_email when write mode is on), WRAPS_ALLOWED_RECIPIENT_DOMAINS (Comma-separated domains the agent may send to. Matching is exact; list subdomains explicitly), WRAPS_HISTORY_TABLE_NAME (DynamoDB table holding email history. Defaults to wraps-email-history), WRAPS_API_KEY (Wraps API key (wraps_...) for the contacts, segments, topics, templates, broadcasts, events, workflows, approvals, metrics, inbound and brand-kit tools. Without it the server falls back to the session from `wraps auth login`; with neither, only the AWS tools are registered), WRAPS_API_URL (Wraps API base URL. Defaults to https://api.wraps.dev; set it for a self-hosted control plane), WRAPS_ORG_ID (Organization id to act in when using a `wraps auth login` session that belongs to several organizations).
Alternatives to Email
same job, measured the same waySend transactional email and check delivery: bounces, suppressions, per-provider stats.
Send email, search delivery logs, and manage domains and your Maileroo account.
Send and manage email, domains, audiences, and API keys through the Resend API.
Send transactional email and manage domains, templates, webhooks and suppressions with Groundmail.
Truncus email MCP server: send, send_sync, validate, events, stats, domains, suppression tools.
Professional email, calendar, contacts and files on your own domain.
Email hosting from your AI: read and send mail, add domains, check DNS and manage mailboxes.
Send email, manage sending domains, and read delivery analytics from your SecureSMTP account.
Email — questions
Answers built from our own checks of this server.