Native MCP tools
Eleven explicit tools cover sends, contacts, templates, broadcasts, domains, and health.
Scoped by domain
Each key can be restricted to a sending-domain sub-account and narrow operations.
Idempotent retries
A stable idempotency key prevents an agent retry from producing duplicate email.
User synchronization
Upsert product users and attributes in batches of up to 1,000.
Versioned templates
Agents can reuse reviewed content instead of inventing every message from scratch.
Inspectable health
Delivery, failures, opens, clicks, domains, and SES connection status stay visible.
A bounded tool, not a blank cheque
The API key is the agent’s contract.
Restrict a key to one domain. Add only the scopes the agent needs. A content agent can prepare a template without sending it. A support agent can send a transactional reply without launching a broadcast.
{
"name": "support-agent",
"domainId": "domain-uuid",
"scopes": ["emails:send", "emails:read", "templates:read"]
}Open source. SES-only. No hidden sending margin.
Run tinysend with Docker and PostgreSQL, connect your AWS role, and point any MCP-compatible agent at the same API your team uses.