generated: '2026-08-13'
method: searched
status: published
source: >-
  https://github.com/awslabs/mcp (server index read 2026-08-13) and a live MCP handshake against
  https://knowledge-mcp.global.api.aws/mcp
deployment:
  mode: both
  endpoint: https://knowledge-mcp.global.api.aws/mcp
  install: uvx awslabs.aws-api-mcp-server@latest
  package: https://github.com/awslabs/mcp/tree/main/src/aws-api-mcp-server
  auth: none
  verified: probed
  note: >-
    The two halves of this deployment block are DIFFERENT PRODUCTS and are recorded together only because the
    contract asks for one block. The remote endpoint is the AWS Knowledge MCP Server — anonymous, callable by
    an agent right now, and it serves DOCUMENTATION, not SES operations. The install line is the local-stdio
    awslabs.aws-api-mcp-server, which does reach SES but requires a human to install it and supply AWS
    credentials first. AWS ships NO SES-specific MCP server of either kind.
servers:
  - name: AWS Knowledge MCP Server
    mode: remote
    transport: streamable-http
    url: https://knowledge-mcp.global.api.aws/mcp
    auth: none
    first_party: true
    ses_specific: false
    verified: probed
    probe:
      date: '2026-08-13'
      initialize:
        http_status: 200
        protocol_version: '2025-03-26'
        server_name: AWSKnowledgeMCP
        server_version: 1.0.0
      tools_list:
        http_status: 200
        tool_count: 5
    tools:
      - name: aws___search_documentation
        description: AWS docs search; each result's context is a verbatim chunk of the actual page.
        required: [search_phrase]
      - name: aws___read_documentation
        description: Fetch a full AWS documentation page as markdown.
        required: []
      - name: aws___retrieve_skill
        description: Retrieve an AWS agent skill (SKILL.md, workflows, references).
        required: [skill_name]
      - name: aws___list_regions
        description: Retrieve a list of all AWS regions.
        required: []
      - name: aws___get_regional_availability
        description: AWS resource availability per region.
        required: [resource_type]
    note: >-
      Zero of these five tools calls an Amazon SES operation. This server answers questions ABOUT SES from the
      documentation corpus; it cannot send an email, verify an identity or read a sending quota.
  - name: awslabs.aws-api-mcp-server
    mode: local-stdio
    transport: stdio
    install: uvx awslabs.aws-api-mcp-server@latest
    package: https://github.com/awslabs/mcp/tree/main/src/aws-api-mcp-server
    auth: api-key
    auth_detail: AWS credentials (IAM access key/secret or an assumed role) resolved from the local environment.
    first_party: true
    ses_specific: false
    verified: searched
    tools:
      - name: call_aws
        description: Execute an AWS CLI command; reaches SES as `aws sesv2 <operation>`.
      - name: suggest_aws_commands
        description: Suggest AWS CLI commands from a natural-language description.
    note: >-
      A generic AWS CLI passthrough. It can invoke any of the 86 SES v2 operations, but it publishes no
      per-operation input schema, so an agent gets no typed contract for SendEmail or anything else. Not
      probed live — a stdio server has no endpoint to probe and requires a local install plus credentials.
absent:
  ses_specific_mcp_server: >-
    Checked every server directory under awslabs/mcp/src on 2026-08-13 (61 servers). There is no
    amazon-ses-mcp-server, no ses-mcp-server and no mail-manager MCP server. SES is one of the larger AWS
    services without a dedicated MCP surface.
agent_surface_summary: >-
  AWS's real agent investment for SES is in Agent Skills, not MCP: github.com/amazon-ses/skills publishes
  first-party aws-ses and aws-mail-manager skills (see skills/_index.yml). An agent reaching SES today either
  loads those skills and drives an SDK, or shells out through the local aws-api-mcp-server. Nothing exposes
  SES operations as typed MCP tools over a URL.
crosswalk: mcp/amazon-ses-tool-crosswalk.yml