Sendable

me.sendablePublished by sendable.mev1.0.3Updated Nov 3, 2026

Send transactional email from your editor — describe the event, Sendable writes and sends it.

VerifiedSTDIODesktop onlyDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Sendable lets an assistant write and send transactional email from the editor by describing an event, with your data values substituted afterwards.

What you can do
  • Send transactional email by describing an event and its fields, letting the service write the message copy.
  • Add new message types by naming a new event string rather than maintaining templates.
  • Keep data values intact: the writing model sees field names only, and placeholders are filled in afterwards.
  • Rely on a second model that checks each draft for claims the data does not support and refuses rather than guessing.
When to use it
Useful when you want an assistant in Claude Desktop or Cursor to send transactional messages such as order or payment notifications without building and maintaining templates or a dashboard step.
Requirements
Runs as a local process via npx from the sendableme-mcp npm package, so Node.js is needed. Requires a Sendable API key supplied in the SENDABLE_API_KEY environment variable; a free key covers 500 messages a month. Desktop client only.
Before you install
The server sends real email to recipients, so a mistaken event or address goes out immediately. It needs the SENDABLE_API_KEY secret, which should be kept out of shared configs. Message content and field names are processed by Sendable's models, so consider what event data you pass.

Installation

In SourceWeft

  1. Open Sendable in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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
js
import { send } from 'sendableme';
await send('[email protected]', '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:

[Run on Replit]

What's in this repo

DirectoryWhat 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.

js
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

Source: README.md at commit 578ffdb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts