PluginBench
MCP Server
Active
MIT

dev.wraps/email MCP Server

dev.wraps/email

RepositoryRegistry
How to choose

What this kind of tool is for

  • Draft, send, or triage messages and email from inside your agent.
  • Pipe notifications from a build or alert into your team channel automatically.
  • Summarize a busy channel thread into the handful of points that matter.

How to compare servers like this

Channel coverage:
Check the specific app (email, chat, notifications) and whether it reads as well as writes.
Scope of access:
Messages are sensitive; review what the tool can see before connecting an account.
Rate behavior:
Bulk-sending tools should respect provider limits — avoid anything that floods.
Maintenance signal:
APIs in this space change often; recent updates are a strong signal.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the dev.wraps/email MCP server?

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

How to install dev.wraps/email

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • 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.

~/Library/Application Support/Claude/claude_desktop_config.json
JSON config
{
  "mcpServers": {
    "email": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "env": {
        "AWS_REGION": "<YOUR_AWS_REGION>",
        "AWS_PROFILE": "<YOUR_AWS_PROFILE>",
        "WRAPS_WRITE_ENABLED": "<YOUR_WRAPS_WRITE_ENABLED>",
        "WRAPS_FROM_EMAIL": "<YOUR_WRAPS_FROM_EMAIL>",
        "WRAPS_ALLOWED_RECIPIENTS": "<YOUR_WRAPS_ALLOWED_RECIPIENTS>",
        "WRAPS_ALLOWED_RECIPIENT_DOMAINS": "<YOUR_WRAPS_ALLOWED_RECIPIENT_DOMAINS>",
        "WRAPS_HISTORY_TABLE_NAME": "<YOUR_WRAPS_HISTORY_TABLE_NAME>"
      }
    }
  }
}

Related MCP servers

WRWraps logo

Wraps

Active

Search Wraps docs and estimate AWS SES costs for your email infrastructure.

61
TypeScript
View repository →

Branded email on your own domain: send, reply, search, aliases, contacts and campaigns.

Give an agent its own inbox: send, receive, and pull signup codes from real email.

0
Python
MIT
View repository →

Create and manage Templated email templates from any MCP client - bring your own model.

Pick the right LLM for any task. Ranked shortlist with rationale across 8 evaluators.

0
Python
MIT
View repository →

Read-only Solana and Robinhood Chain tools: wallet recovery, token safety, unlocks, upgrades, fees.