Skip to main content
Glama

Sessy — Amazon SES observability

Server Details

Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
marckohlbrugge/sessy
GitHub Stars
907
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 7 tools

Disambiguation4/5

Each tool has a clearly distinct action-resource focus: list_sources, create_source, update_source, get_source_setup, email_stats, search_events, and get_message are easy to tell apart. The one soft overlap is that create_source also returns AWS SES wiring details (webhook URL, config set, setup steps) that get_source_setup returns, but the new-vs-existing distinction in the descriptions keeps them separable.

Naming Consistency4/5

Six of seven tools follow a clean verb_noun snake_case pattern (create_source, get_source_setup, list_sources, update_source, search_events, get_message). The lone deviation is email_stats, which is noun_noun rather than a verb form, but it remains readable and predictable.

Tool Count5/5

Seven tools is well-scoped for an SES observability service: three source lifecycle tools, two event/message retrieval tools, one aggregate stats tool, and one setup helper. Each tool earns its place with no redundant entries.

Completeness4/5

The surface covers the full observability lifecycle — create/read/update sources, search events, drill into individual messages, and aggregate stats — with clear guidance on paging via search_events. The only gap is source deletion and retention changes, which are explicitly and deliberately delegated to the web UI, so it is a documented limitation rather than a dead end.

Available Tools

7 tools
create_sourceCreate sourceAInspect

Create a new email source (one per app or mail stream) and return the AWS SES wiring details for it: webhook URL for the SNS subscription, suggested configuration set and topic names, and the remaining setup steps. Retention is configured in the web UI.

Inputs: name (required), color. Returns: setup, source

email_statsEmail statsA
Read-onlyIdempotent
Inspect

Aggregate email stats for one source or the whole account over a date range: counts by event type, unique opens/clicks, bounce/complaint/open/click rates, bounce breakdown by subtype, and an optional daily time series. Rates are percentages of sends.

Inputs: to_date, from_date, source_id, date_range, +1 more. Returns: hint, scope, counts, daily_series, +3 more

get_messageGet messageA
Read-onlyIdempotent
Inspect

Fetch one email by its ses_message_id (from search_events results): subject, sender, destinations, SES tags, and the per-recipient event timeline including bounce/complaint diagnostics (first 500 events; events_truncated flags the rest — use search_events to page through them).

Inputs: ses_message_id (required). Returns: events, message, events_truncated

get_source_setupGet source setupA
Read-onlyIdempotent
Inspect

Fetch one source's settings and the AWS SES wiring details for it: webhook URL for the SNS subscription, suggested configuration set and topic names, and the remaining setup steps. Use this to finish or verify SES setup for an existing source.

Inputs: source_id (required). Returns: setup, source

list_sourcesList sourcesA
Read-onlyIdempotent
Inspect

List this account's email sources with 30-day health stats (sent count, bounce rate, last event). Start here: the other tools take a source_id from these results.

Inputs: no named parameters. Returns: sources, guidance

search_eventsSearch eventsA
Read-onlyIdempotent
Inspect

Search email events (sends, deliveries, bounces, complaints, opens, clicks), newest first. Returns compact rows; use get_message with a row's ses_message_id for the full timeline. The date window defaults to the last 30 days — pass date_range "all_time" to search everything.

Inputs: limit, query, cursor, to_date, +5 more. Returns: hint, events, has_more, next_cursor, +1 more

update_sourceUpdate sourceA
Idempotent
Inspect

Rename a source or change its badge color. Omitted fields are left unchanged. Retention and deletion are deliberately not available here — use the web UI.

Inputs: source_id (required), name, color. Returns: setup, source

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only search and retrieval of archived emails, archive statistics, health, and ingestion sources, with an optional administrative toolset for user, role, reindexing, and queue management.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and manage email deliverability data — bounces, complaints, suppressions, delivery stats, and campaigns — across multiple providers like AWS SES, SendGrid, Mailgun, and Postmark.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Send transactional email and manage domains, API keys, webhooks, contacts and broadcasts through SpacePost, a Resend-compatible email API on Amazon SES. One tool per API endpoint, with read-only and send-only modes.
      797 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.