me.sendable/sendable MCP Server

This MCP server enables sending transactional email from an editor. The system takes an event description; Sendable writes the corresponding message and sends it. It uses one integration flow where message types are identified as strings, with payload data provided for the event details.

🛠️ Key Features

Transactional email delivery via Sendable
Event-driven messaging: “describe the event” to generate/send the message
Message types provided as strings (e.g., order_shipped)
Uses TypeScript/JavaScript integration (npm i sendableme)

🚀 Use Cases

Order lifecycle notifications such as “order shipped”
Editor-triggered transactional messaging (send from your development environment)

⚡ Developer Benefits

Complete integration with a single send call
No templates to maintain (message words are generated around provided data)
Example payload fields include orderId and eta

⚠️ Limitations

Source material does not specify supported channels beyond transactional email, authentication details, or delivery guarantees
Tool count and full MCP tool list are not provided in the available data

Sendable

One line, and your app knows how to talk to its users.

You describe what happened; Sendable writes the message and sends it. No templates to maintain, no dashboard step — your data is never rewritten, only the words around it.

bash

npm i sendableme

import { send } from 'sendableme';

await send('sam@example.com', 'order_shipped', { orderId: 'A-1042', eta: 'Friday' });

That's a complete integration. Adding a new message type is a new string.

Get a free API key at sendable.me/keys — 500 messages a month, no card.

Try it in your browser

One click imports the SaaS-welcome example and runs it on Replit — add your SENDABLE_API_KEY in Secrets and hit Run:

What's in this repo

Directory	What it is
`sdk/`	The `sendableme` npm package — the client SDK
`mcp/`	`sendableme-mcp` — an MCP server, so Claude and Cursor can send email by asking
`templates/`	Three runnable examples against the live API

Your data is never rewritten

The model that writes the copy never sees your values — only your field names. It writes copy containing {{placeholders}}, and your values are substituted afterwards, so a price, a date, or a reset link cannot be altered. A second model checks every draft for claims your data doesn't support and refuses rather than guess.

await send(user.id, 'payment_failed', { amount: '$99.00' });
// "$99.00" appears exactly as written, always

MCP

bash

npx -y sendableme-mcp

Add it to Claude Desktop or Cursor and send transactional email straight from the editor. See mcp/ for the config block.

Docs

Full reference, written to be pasted into an AI assistant: sendable.me/llms.txt

License

MIT

me.sendable/sendable