Can I use Amazon SES as a CLI?

Yes. KosmoKrator exposes a Amazon SES CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Amazon SES through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Amazon SES tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Amazon SES credentials stored?

Amazon SES credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Amazon SES MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

Amazon SES MCP Integration for Codex

Connect Amazon SES to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 4 read 2 write Bearer token auth

Submit Amazon SES feedback View package source

Connect Amazon SES to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Amazon SES MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-amazon-ses": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=amazon-ses",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=amazon-ses --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Amazon SES instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Amazon SES Tools Visible to Codex

Codex sees stable MCP tool names generated from the Amazon SES integration catalog.

MCP tool	Source function	Type	Description
`integration__amazon_ses__amazonses_send_email`	`amazon-ses.amazonses_send_email`	Write	Send an email via Amazon SES. Specify the sender, recipient(s), subject, and body (HTML and/or plain text). Optionally reference a template or add reply-to addresses.
`integration__amazon_ses__amazonses_get_template`	`amazon-ses.amazonses_get_template`	Read	Retrieve an email template from Amazon SES by its name. Returns the template subject, HTML body, and text body.
`integration__amazon_ses__amazonses_list_templates`	`amazon-ses.amazonses_list_templates`	Read	List all email templates in Amazon SES. Returns template names and creation timestamps. Supports pagination.
`integration__amazon_ses__amazonses_create_template`	`amazon-ses.amazonses_create_template`	Write	Create a new email template in Amazon SES. Templates can include HTML and plain text content with optional substitution variables (e.g., {{name}}).
`integration__amazon_ses__amazonses_list_suppressions`	`amazon-ses.amazonses_list_suppressions`	Read	List email addresses on the suppression list for a specific configuration set in Amazon SES. Suppressed addresses will not receive emails.
`integration__amazon_ses__amazonses_get_current_user`	`amazon-ses.amazonses_get_current_user`	Read	Get the currently authenticated user for the Amazon SES integration. Useful for verifying credentials and account information.

Related Amazon SES Pages

Amazon SES CLIUse direct JSON commands instead of MCP discovery. Amazon SES MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.