Skip to content

docs: Add AWS SES MCP server reference to community list #2141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

CrazyFrog007
Copy link

@CrazyFrog007 CrazyFrog007 commented Jun 17, 2025

Description

Add reference to sample MCP Server for Amazon SES (SESv2) in the README.md with a link to the GitHub repository and AWS blog post for more details.

Server Details

  • Server: Sample MCP Server for Amazon SES (SESv2)
  • Changes to: README.md file - adding the MCP server to the community servers list

Motivation and Context

This change adds a reference to the Amazon SES (SESv2) MCP server in the community servers list to increase visibility and adoption. The SESv2 MCP server enables LLM clients to interact with Amazon SES APIs, allowing for email sending and management capabilities through natural language.

How Has This Been Tested?

I've tested this MCP server with the scenarios described in the AWS blog post Use AI agents and the Model Context Protocol with Amazon SES. These scenarios include email sending, template management, and verification operations through natural language.

Breaking Changes

N/A

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

N/A

@CrazyFrog007 CrazyFrog007 force-pushed the CrazyFrog007docs/add-ses-mcp-reference branch 5 times, most recently from a02943c to 4255699 Compare June 25, 2025 16:59
@CrazyFrog007 CrazyFrog007 force-pushed the CrazyFrog007docs/add-ses-mcp-reference branch 3 times, most recently from b31d69d to 9e29e14 Compare July 1, 2025 19:17
@CrazyFrog007 CrazyFrog007 force-pushed the CrazyFrog007docs/add-ses-mcp-reference branch 2 times, most recently from 4667e9b to bf59a08 Compare July 10, 2025 18:55
@CrazyFrog007 CrazyFrog007 changed the title docs: Add sample AWS SES MCP server reference to community list docs: Add AWS SES MCP server reference to community list Jul 10, 2025
@CrazyFrog007 CrazyFrog007 force-pushed the CrazyFrog007docs/add-ses-mcp-reference branch from bf59a08 to 83bb15d Compare July 11, 2025 16:18
@olaservo olaservo added the add-community-server This pull request adds a link to a community-created server. label Jul 11, 2025
@@ -405,6 +405,7 @@ A growing set of community-developed and maintained servers demonstrates various
- **[AWS Cost Explorer](https://github.com/aarora79/aws-cost-explorer-mcp-server)** - Optimize your AWS spend (including Amazon Bedrock spend) with this MCP server by examining spend across regions, services, instance types and foundation models ([demo video](https://www.youtube.com/watch?v=WuVOmYLRFmI&feature=youtu.be)).
- **[AWS Resources Operations](https://github.com/baryhuang/mcp-server-aws-resources-python)** - Run generated python code to securely query or modify any AWS resources supported by boto3.
- **[AWS S3](https://github.com/aws-samples/sample-mcp-server-s3)** - A sample MCP server for AWS S3 that flexibly fetches objects from S3 such as PDF documents.
- **[AWS SES](https://github.com/aws-samples/sample-for-amazon-ses-mcp)** Sample MCP Server for Amazon SES (SESv2). See [AWS blog post](https://aws.amazon.com/blogs/messaging-and-targeting/use-ai-agents-and-the-model-context-protocol-with-amazon-ses/) for more details.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR - should these aws-samples links actually go in the Official section?

Copy link
Author

@CrazyFrog007 CrazyFrog007 Jul 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR - should these aws-samples links actually go in the Official section?

@olaservo, based on the description, the official section includes production-ready MCP servers, but the sample is not intended for use in a production environment at this time. For this reason, I placed it under the Community section even though the sample is official. Let me know if you think it would make more sense to move the sample to the Official section with a note such as (Not intended for production use).

@olaservo olaservo added waiting for submitter Waiting for the submitter to provide more info and removed add-community-server This pull request adds a link to a community-created server. labels Jul 11, 2025
@CrazyFrog007 CrazyFrog007 force-pushed the CrazyFrog007docs/add-ses-mcp-reference branch from 83bb15d to f9df487 Compare July 11, 2025 20:06
Add reference to sample MCP Server for Amazon SES (SESv2) in the README.md
with a link to the GitHub repository and AWS blog post for more details.
@CrazyFrog007 CrazyFrog007 force-pushed the CrazyFrog007docs/add-ses-mcp-reference branch from f9df487 to 202341f Compare July 15, 2025 18:07
@olaservo
Copy link
Member

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2370

This is a new process we're trying out, so if you see any issues feel free to re-open the PR and tag me.

@olaservo olaservo closed this Jul 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for submitter Waiting for the submitter to provide more info
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants