Sessy — Amazon SES observability
io.github.marckohlbrugge由 GitHub 帳號 marckohlbrugge 發布v1.0.0更新於 Oct 24, 2026
Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.
概覽
唯讀的 Amazon SES 可觀測性伺服器,讓助理搜尋郵件事件、檢查退信並取得投遞統計。
- 可以做什麼
- 搜尋與檢視郵件事件,包括單封郵件的完整投遞時間軸與退信診斷
- 取得 SES 寄送的彙總投遞統計
- 建立與重新命名來源
- 取得 SES 串接資訊,例如 webhook 網址、組態集與主題名稱,用來端到端設定新應用程式
- 適用情境
- 當你透過 Amazon SES 寄送郵件,並希望 AI 編碼助理不必開啟網頁介面就能追查寄出後的情況——例如追蹤退信、查看投遞時間軸或為新應用程式串接 SES——時適用。
- 執行需求
- 需要遠端 MCP 端點(api.sessy.do,或自架執行個體的 /mcp 路徑)。需在網頁介面建立 Sessy API 金鑰,並以 Authorization bearer 權杖送出。自架可透過 Docker 執行;Cloudflare 或 CDN 的機器人防護需對 /mcp 路徑放行。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Sessy — Amazon SES observability,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.marckohlbrugge%2Fsessy/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"sessy-amazon-ses-observability": {
"type": "http",
"url": "https://api.sessy.do/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
Sessy
Open-source email observability for AWS SES by Marc Köhlbrugge.
What is Sessy?
Amazon SES is a fantastic email service: cost-effective, reliable, and great deliverability. But it's frustratingly difficult to see what's actually happening with your emails.
That's why many people turn to overpriced email services that are often just glorified SES wrappers with a nice UI. You end up paying a lot for something you could do yourself.
Sessy is the open-source alternative. Use raw SES and still get a beautiful interface to see what happens after you hit send: deliveries, bounces, complaints, opens, clicks, and more.
[Sessy screenshot]Running your own Sessy instance
The easiest way to run Sessy is with Docker:
See Docker deployment docs for full configuration options.
Want to deploy your own modified version? See Kamal deployment docs for deploying from a fork.
Using Dokku? See Dokku deployment docs.
Need help configuring AWS SES itself? See AWS SES setup guide.
For hardening recommendations, see SES security and deliverability best practices.
MCP server for AI agents
Sessy ships an MCP server at /mcp, so AI coding agents (Claude Code, Cursor, Codex) can query your email data: search events, inspect a message's full delivery timeline with bounce diagnostics, and pull aggregate stats. Agents can also create and rename sources and fetch the SES wiring details (webhook URL, configuration set and topic names) to set up a new app end to end. Email data is read-only; retention settings and deleting sources stay in the web UI.
Create an API key on the API keys page in the web UI, then follow the connect instructions at /docs/mcp on your instance. For example, for Claude Code:
Two things worth knowing:
- Cloudflare / CDN users: bot protection (managed challenges) blocks MCP clients. Exempt the
/mcppath from bot protection or agent requests will fail. - HTTP Basic auth:
/mcpauthenticates with API keys only and ignoresHTTP_AUTH_*. Enabling HTTP Basic later does not revoke previously created API keys — review the API keys page after locking down an install.
Hosted version
We're working on a managed version of Sessy for those who'd rather not run their own instance.
You'll notice references to it in this codebase: a saas/ directory, Gemfile.saas, and the occasional Sessy.saas? check. These power the hosted version and are intentionally kept in this repository for simplicity, rather than maintaining separate repos. None of it affects self-hosting: the default bundle ignores the saas/ engine entirely, and the test suite verifies the open-source version behaves identically without it.
Jobs dashboard
Sessy uses Solid Queue for background jobs. A web dashboard is available at /jobs to monitor queues, retry failed jobs, and view recurring tasks.
Development
You are welcome to modify Sessy to your liking.
To get started:
Contributing
We welcome contributions! Since we're still in a very early stage, please keep the following in mind:
- Typos and obvious bugs: Feel free to submit a PR directly.
- Code changes: Please try to match our existing style.
- New features: Please open an issue first to discuss before implementing.
- Deployment docs: We keep first-party deployment docs focused on broad, open, self-hosted paths we actively use (for example Docker, Kamal, and Dokku). We generally do not add provider-specific deployment guides to this repository.
For anything beyond small fixes, please open an issue first so no one wastes their time on something we might not merge.
License
Sessy is released under the O'Saasy License, except where a subdirectory specifies otherwise (for example, the Claude and Cursor plugin packages are MIT).
Inspiration
Sessy was heavily inspired by Fizzy and we're grateful to 37signals for open-sourcing their codebase.
來源:README.md,提交 1ebbe41
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。

