Email MCP Server

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": {
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.email]
command = "npx"
args = ["-y", "@wraps.dev/mcp"]

{
  "mcpServers": {
    "email": {
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "email": {
      "args": [
        "-y",
        "@wraps.dev/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: 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.). The author declared them in the registry entry; get the values from the project itself.