
Sessy MCP Server: Setup for Claude Code, Cursor and Other Apps
Lets Claude, Cursor and other assistants search your Amazon SES email events and stats through Sessy, and set up new email sources.
Sessy is a self-hostable dashboard for Amazon SES email events, and its MCP server is built into the app. Your assistant can search events, read a message's full delivery timeline with bounce reasons, pull stats, and create or rename sources. Email data is read-only.
You need a Sessy account or your own Sessy install, and an API key from its API keys page. The server runs at Sessy's hosted address or at /mcp on your own instance. Subjects and addresses in your mail are third-party text, so treat them as data when an assistant reads them.
Good for
- Developers who send email through Amazon SES and want to ask why a message bounced
- Teams that already use or self-host Sessy to watch deliverability
- Anyone wiring a new app to SES who wants the setup steps in chat
Works in
14 should work
Tap an app to see how to set it up and any known problems.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Supports hosted MCP servers.
Install Sessy MCP
Claude Code
- 1
Copy this prompt.
Add the Sessy MCP server to Claude Code. Run this command: claude mcp add --transport http sessy https://api.sessy.do/mcp --header "Authorization: Bearer YOUR_API_KEY" Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Sessy API key.
The endpoint shown is Sessy's hosted address. If you run Sessy yourself, use https://your-sessy-host/mcp instead. Put your own API key where it says YOUR_API_KEY.
From the project README. Source.
Tools
Lists your email sources with 30-day health
Shows each source (one per app or mail stream) with messages sent in the last 30 days, bounce rate and time of the latest event. Other tools take a source ID from this list.
Try: “Which of my email sources have the highest bounce rate this month?”
Read ·
list_sourcesFinds sends, bounces, complaints, opens and clicks
Searches email events newest first, by recipient address or subject, event type, bounce subtype and date range. It defaults to the last 30 days and returns up to 100 rows per page.
Try: “Find all bounces to gmail.com addresses in the last week.”
Read ·
search_eventsShows one email's full delivery timeline
Looks up a single email by its SES message ID and returns subject, sender, recipients, tags and every event per recipient, including bounce and complaint diagnostics.
Try: “Show me what happened to message 0100018f-example.”
Read ·
get_messageCounts and rates for a source or the whole account
Returns totals for sent, delivered, bounced, complaints, opens and clicks, plus rates, a bounce breakdown and an optional day-by-day series for up to 120 days.
Try: “Give me last month's delivery and complaint rates for the newsletter source.”
Read ·
email_statsShows the AWS wiring details for a source
Returns a source's settings plus what you need on the AWS side: the webhook URL for the SNS subscription, suggested configuration set and topic names, and the remaining setup steps.
Try: “What do I still need to set up in SES for the billing source?”
Read ·
get_source_setupCreates a new email source and returns setup steps
Adds a source with a name and optional badge color, then returns the SES wiring details. Calling it twice with the same name creates two sources.
Try: “Create a source called 'Mobile app' and tell me how to connect SES.”
Write ·
create_sourceRenames a source or changes its color
Changes only the name or badge color of an existing source. Retention settings and deletion are not available through the server.
Try: “Rename source 3 to 'Marketing emails'.”
Write ·
update_source
Read from the source code
Permissions
medium risk · 4 things to watch
Medium risk
The assistant can read all email events in your Sessy account and create or rename sources. Use a dedicated API key and revoke it when you stop using the server.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
One API key reaches all of the account's email data
The Sessy docs say a key grants access to all email data in the account and can create and rename sources. Treat it like a password and revoke unused keys. github.com
It can create and rename sources
create_source and update_source change source names and colors only. Retention settings and deleting sources are not offered and stay in the web UI. github.com
Email text comes from other people
Subjects, recipient addresses and bounce messages are third-party content. The server tells the assistant to treat them as data, but review any source change the assistant proposes. github.com
Rate limits apply
The endpoint allows 60 requests a minute per key and 10 a minute for invalid keys. github.com
Security advisories
No published security advisories as of Nov 1, 2026.
Technical details
| Turning on read-only | No read-only switch is documented. Email data is read-only by design. The tools that write only create or rename sources. |
|---|---|
| Talks to | Sessy (api.sessy.do, or your own Sessy host) |
| Sign-in and keys | A Sessy API key sent as a bearer token. It sits in your editor's config file. |
Questions
Is the Sessy MCP server official?
Yes, for Sessy. It is built into the Sessy app by its author, Marc Köhlbrugge. It is not made by Amazon or AWS.
Do I need a Sessy account?
Yes. You need a Sessy account or your own Sessy install, because the server reads that account's email data. Create an API key on its API keys page.
Can I use it with ChatGPT?
Not yet. The Sessy docs say ChatGPT custom connectors need OAuth, which Sessy does not support, and list it as planned.
Is the data read-only?
Email data is read-only. The only changes it can make are creating a source and changing a source's name or color.
Can I use it with a self-hosted Sessy?
Yes. Point the server address at /mcp on your own instance and use an API key from that instance. If it sits behind Cloudflare, exempt that path from bot protection or requests fail.
Is there a hosted Sessy, or do I run it myself?
Both are described. The README says the maker is still working on a managed version, and its docs tell you to run your own instance. The MCP docs and registry file, server.json, list https://api.sessy.do/mcp as the hosted address, so confirm that your account exists there before you rely on it.
What license is Sessy under?
The O'Saasy License. Its LICENSE file grants permission to use, copy, modify, distribute and sell the software, with one condition: you may not offer it to third parties as a hosted or SaaS product that competes with the original licensor, where the product's main value is the software itself. The repo's Claude and Cursor plugin packages are MIT. Read the LICENSE file before you build a service on it.
How do I add it to Claude Code or Cursor?
Use the matching tab in the install box above and put your API key in the header.
Information
updated Nov 2, 2026
- Publisher
- Official
- Endpoint
https://api.sessy.do/mcp- Transport
- Streamable HTTP
- Auth
- API key
- Version
- 1.0.0
- License
- O'Saasy License
- Last commit
- Oct 30, 2026
- Open issues
- 0
- Listed in
- Official MCP registry
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 5Hide
- MCP docs view · github.com
- server.json · github.com
- README · github.com
- mcp_server.rb · github.com
- LICENSE.md · github.com