AWS SES MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| aws_region | No | AWS region (default: us-east-1) | us-east-1 |
| from_email | Yes | Verified sender email address for SES | |
| aws_access_key_id | Yes | AWS access key ID for SES | |
| aws_secret_access_key | Yes | AWS secret access key for SES |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailC | Send an email using AWS SES. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single action is clearly defined.
The tool uses a clear verb_noun pattern (send_email), which is predictable and readable. There are no other tools to create inconsistency.
A single tool is quite thin for a server ostensibly covering AWS SES. While send_email is a core operation, the surface feels under-scoped.
SES involves identity verification, template management, and bulk sending, none of which are exposed. The tool set only covers one basic operation, leaving significant lifecycle gaps.