This is a simple MCP server that sends emails using AWS SES (Simple Email Service). Perfect for integrating with Cursor or Claude Desktop to compose
Aws ses mcp mcp server connects Aws Ses MCP to AI assistants that speak the Model Context Protocol. This is a simple MCP server that sends emails using AWS SES (Simple Email Service). Perfect for integrating with Cursor or Claude Desktop to compose and send emails directly without copy-pasting. The service supports both plain text and HTML emails with advanced features like CC, BCC, and reply-to.
This is a simple MCP server that sends emails using AWS SES (Simple Email Service). Perfect for integrating with Cursor or Claude Desktop to compose and send emails directly without copy-pasting. The service supports both plain text and HTML emails with advanced features like CC, BCC, and reply-to functionality.
The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 8 environment variables: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, SENDER_EMAIL_ADDRESS, REPLY_TO_EMAIL_ADDRESSES, YOUR_AWS_ACCESS_KEY_ID, YOUR_AWS_SECRET_ACCESS_KEY, YOUR_AWS_REGION. Keep credentials in your client's env block or a secrets manager rather than committing them.
Before you begin, ensure you have: 1. AWS SES account set up and configured 2. Verified email domain or individual email addresses in AWS SES 3. AWS credentials (Access Key ID and Secret Access Key) with SES permissions 4. Node.js installed on your system
Communication servers earn their keep on volume — summarising channels and threads that would otherwise cost you an hour of scrollback. Aws Ses MCP sits in that group. Worth comparing against the other communication servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
{
"mcpServers": {
"aws-ses": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"AWS_ACCESS_KEY_ID": "your-value",
"AWS_SECRET_ACCESS_KEY": "your-value",
"AWS_REGION": "your-value",
"SENDER_EMAIL_ADDRESS": "your-value",
"REPLY_TO_EMAIL_ADDRESSES": "your-value",
"YOUR_AWS_ACCESS_KEY_ID": "your-value",
"YOUR_AWS_SECRET_ACCESS_KEY": "your-value",
"YOUR_AWS_REGION": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Before you begin, ensure you have: 1. AWS SES account set up and configured 2. Verified email domain or individual email addresses in AWS SES 3. AWS credentials (Access Key ID and Secret Access Key) with SES permissions 4. Node.js installed on your system
| Variable | Description | Required |
|---|---|---|
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| AWS_REGION | Configuration value read at startup. | Optional |
| SENDER_EMAIL_ADDRESS | Configuration value read at startup. | Optional |
| REPLY_TO_EMAIL_ADDRESSES | Configuration value read at startup. | Optional |
| YOUR_AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| YOUR_AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| YOUR_AWS_REGION | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.