Email MCP Server

Email is an MCP integration. Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.

Packages and local setup

The published npm package is @wraps.dev/mcp, version 0.8.2. Its declared MCP transport is stdio.

The package declares 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.8.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related communication MCP servers for tools that cover the same kind of work.