Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.
Connect Remote server
claude mcp add --transport http sessy https://api.sessy.do/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"sessy": {
"url": "https://api.sessy.do/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"sessy": {
"type": "http",
"url": "https://api.sessy.do/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.sessy.do/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer token from your Sessy API keys page (https://app.sessy.do/api_keys). Self-hosters: point the URL at your own instance's /mcp endpoint instead of api.sessy.do. Setup: https://sessy.do/docs/mcp |
Details
| Endpoint | https://api.sessy.do/mcp (Streamable HTTP) |
| First published | 31 Jul 2026 |
| Last updated | 31 Jul 2026 |
| Registry name | io.github.marckohlbrugge/sessy |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
