Productivity · Local MCP server
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.wraps/email- Version
- 0.8.2
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- dev.wraps · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain wraps.dev · how
- Listed under
- Email MCP servers, Amazon MCP servers
- Website
- wraps.dev
- Repository
- github.com/wraps-team/wraps-js (folder packages/mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @wraps.dev/mcp | 0.8.2 | stdio |
How to connect Email
Email runs locally from a Node.js package published to the npm registry: @wraps.dev/mcp version 0.8.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @wraps.dev/mcp@0.8.2. It reads these environment variables: AWS_REGION, AWS_PROFILE, WRAPS_WRITE_ENABLED, WRAPS_FROM_EMAIL, WRAPS_ALLOWED_RECIPIENTS, WRAPS_ALLOWED_RECIPIENT_DOMAINS and WRAPS_HISTORY_TABLE_NAME; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"email": {
"command": "npx",
"args": [
"-y",
"@wraps.dev/mcp@0.8.2"
],
"env": {
"AWS_REGION": "<value>",
"AWS_PROFILE": "<value>",
"WRAPS_WRITE_ENABLED": "<value>",
"WRAPS_FROM_EMAIL": "<value>",
"WRAPS_ALLOWED_RECIPIENTS": "<value>",
"WRAPS_ALLOWED_RECIPIENT_DOMAINS": "<value>",
"WRAPS_HISTORY_TABLE_NAME": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from dev.wraps
| Server | Runs |
|---|---|
| WrapsSearch the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication. | Remote · HTTPLive check: ✓ handshake |
More productivity servers
| Server | Runs |
|---|---|
| Elicitation AuditorMCP elicitation anti-patterns: secrets in forms, third-party authorize URLs, credentials in URLs. | Local · stdio |
| ElicitlyHuman-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor. | Local · stdio |
| em[ai]lRead and draft email you forward to a private alias. Agents cannot send or delete mail. | Remote · HTTP |
| EmailEmail infrastructure for AI agents - send, receive, search, and reply to email over MCP. | Remote · HTTPLive check: ✓ handshake |
| EmailMCP server for Blip disposable email - create inboxes, receive emails, extract OTP codes. | Local · stdio |
| Email (IMAP/SMTP)Multi-account IMAP/SMTP email server with 22 tools for reading, sending, searching, and organizing. | Local · stdio |
| Email (IMAP/SMTP)Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers. | Local · stdio |
| Email AgentEmail for AI agents - send, receive as a webhook, manage domains, templates, routing. | Remote · HTTPLive check: sign-in required |