Sessy — Amazon SES observability

What Sessy — Amazon SES observability does

Sessy — Amazon SES observability adds an MCP endpoint to a self-hosted Sessy deployment, allowing compatible AI coding agents to query Amazon SES-related email data. Sessy’s web application provides visibility into deliveries, bounces, complaints, opens, clicks, and other email activity; the MCP interface exposes a subset of that information for agent workflows.

The email data exposed through MCP is read-only. Agents can search events, inspect an individual message’s delivery history, review bounce diagnostics, and retrieve aggregate statistics. They can also create and rename sources and obtain the SES configuration details needed to connect another application, including the webhook URL, configuration set name, and topic names.

How it works

The MCP endpoint is available at /mcp on the Sessy host. An agent authenticates with an API key created from Sessy’s API keys page, sending it as a bearer token. The repository gives a Claude Code example using HTTP transport and the instance URL, followed by an Authorization header.

This arrangement is useful for incident investigation and operational questions: an agent can locate relevant events, follow a message through its delivery timeline, examine a bounce, or compare aggregate results. Configuration tasks can use the source-management and SES-wiring capabilities, while retention changes and source deletion remain in the web interface rather than the MCP API.

Setup and configuration

Run a Sessy instance before connecting an agent. The documented Docker deployment publishes port 80, sets SECRET_KEY_BASE, optionally disables SSL for the container setup, and mounts the Rails storage volume. Docker, Kamal, and Dokku deployment paths are documented by the project, and a separate guide covers AWS SES configuration.

After deployment, create an API key in the web UI and follow the connection instructions at /docs/mcp on that instance. For a direct HTTP connection, use the /mcp URL and pass the key as a bearer token. If the host is behind Cloudflare or another CDN with bot protection, exempt /mcp from managed challenges; otherwise MCP client requests can fail.

HTTP Basic authentication does not authenticate this endpoint. MCP uses API keys, and enabling HTTP Basic later does not revoke keys that already exist, so review the API keys page after changing access controls.

Tools and capabilities

Sessy — Amazon SES observability provides capabilities for:

• Searching email events.
• Inspecting a message’s complete delivery timeline.
• Reviewing bounce diagnostics.
• Pulling aggregate delivery statistics.
• Creating and renaming sources.
• Fetching SES wiring details, including webhook, configuration set, and topic names.

These operations support read-only email investigation plus limited source and setup administration.

Limitations and notes

The MCP interface does not provide retention-setting controls or source deletion; those actions remain available in Sessy’s web UI. Access also depends on a reachable self-hosted instance and a valid API key. CDN bot protection must allow the /mcp path, and HTTP Basic credentials cannot replace MCP API-key authentication.

The repository describes the hosted version as still in development. Its self-hosting instructions and MCP connection model apply to an instance you operate. The project is released under the O'Saasy License, with separate licensing noted for some subdirectories such as the Claude and Cursor plugin packages.