Changelog

​

SDK/MCP release: an outputSchema on every tool

• Every MCP manifest tool now declares an outputSchema (McpToolSpec.outputSchema, plus one exported *Output Zod shape per tool in @senderkit/sdk/mcp) describing its structured result. The hosted server at mcp.senderkit.com advertises these via tools/list and returns every result as structuredContent alongside the existing JSON text. See Structured results.
• Message results no longer include internal identifiers on the hosted MCP server: senderkit_messages_list and senderkit_messages_get return the public publicId but not the database row id, workspace id, or provider-connection id. The REST API’s GET /v1/messages responses are unchanged.
• Exports the TEMPLATE_STATUSES, INBOUND_MESSAGE_STATUSES, INBOUND_DOMAIN_KINDS, and INBOUND_DOMAIN_STATUSES enums the shapes use.
• The CLI-bundled stdio server is unchanged in this release (it does not declare output schemas yet).

​

Twilio SMS delivery status tracking now works

​

SDK/CLI/MCP release: explicit safety hints on every tool

• Every MCP tool now states all three safety hints explicitly — readOnlyHint, openWorldHint, and destructiveHint — instead of leaving some to a client’s inferred defaults. senderkit_send and senderkit_send_raw are the only tools with openWorldHint: true, since they’re the only ones that deliver messages to recipients outside SenderKit; every read-only tool now also states openWorldHint: false and destructiveHint: false directly.
  For TypeScript consumers, this widens the SDK’s ToolAnnotations type: code that previously constructed a partial value (e.g. { readOnlyHint: true }) must now supply all three hints.
• The inbound message verdicts field description is now provider-neutral — it describes scanning verdicts (spam/virus/SPF/DKIM) without naming the underlying receiving infrastructure. The field’s shape and runtime values are unchanged.
• senderkit_send_raw’s scheduledAt field documents the same “must be in the future, within 30 days” constraint as senderkit_send, and its subject/html fields now state they’re required when channel is "email".

​

SDK/CLI/MCP release: SMS recipient format

• senderkit_send_raw’s to field now spells out the per-channel recipient formats, including the E.164 requirement for sms — matching senderkit_send, which already documented it. This flows through to the senderkit send-raw CLI help.
• The SDK README’s SMS example now notes the E.164 requirement and the 400 invalid_recipient response.

​

SDK/CLI/MCP release: inbound tool corrections

• senderkit_inbound_addresses_create is annotated destructiveHint: false — creating an address is additive and fully reversed by deleting it, so well-behaved clients no longer prompt for confirmation on it.
• localPart documents the real format: 1-64 characters of a-z, 0-9, ., _, -, must start and end alphanumeric, lowercased automatically, some names reserved — plus the "*" catch-all shorthand.
• webhookEndpointId documents the full binding behavior: a bound endpoint receives message.received even if it isn’t itself subscribed to that event, but it must be active and share the address’s livemode; left unset, the event fans out to every active subscribed endpoint in the address’s mode.
• livemode no longer implies a quota exemption. The field now states plainly that every inbound address, test or live, counts toward the plan’s inbound-address limit, and that a test-mode address’s forwardTo is recorded as a test send rather than actually delivered.
• senderkit_inbound_messages_list and senderkit_inbound_messages_get were retitled “List Inbound Messages” / “Get Inbound Message” for consistency with the rest of the tool suite.

​

SDK/CLI/MCP release: manifest wire-contract fixes

• cc / bcc are documented as JSON arrays, capped at 50 recipients. senderkit_send and senderkit_send_raw now say so directly, matching the API’s existing limit. The CLI keeps accepting comma-separated values via its own flag help — nothing changes for CLI users.
• List limits are enforced in the schema, not just the description. senderkit_messages_list.limit is bounded 1–200 (default 50); senderkit_inbound_messages_list.limit enforces the 1–100 range its description already claimed. An out-of-range value now fails validation instead of being silently clamped server-side.
• Additive writes carry an honest annotation. Tools that only create something new — senderkit_templates_create and senderkit_inbound_addresses_create — now declare destructiveHint: false instead of true, so well-behaved MCP clients don’t demand confirmation for a reversible, non-destructive call.

​

Clearer send errors, plus stricter recipient and cursor validation

• Field-specific validation errors. A malformed senderkit_send / senderkit_send_raw call — e.g. an email send missing subject or html — now names the offending field (invalid_request: subject Required) instead of a generic Invalid input message. The equivalent POST /v1/send / POST /v1/send-raw REST error issues array gained the same precision.
• SMS recipients are validated as E.164. to on an SMS send must now be a valid E.164 phone number (e.g. +14155551234); previously a malformed value was accepted and simulated as delivered instead of being rejected.
• before on inbound message listing is validated strictly. senderkit_inbound_messages_list.before and GET /v1/inbound/messages?before= now reject a non-ISO-8601 value with a clear invalid_request error instead of silently returning an empty page.

​

SDK/CLI/MCP release: inbound namespace + suppressed status type

• client.inbound — a new namespace with addresses (list, create, delete), messages (list, get, raw, attachment), and domains (list, create, delete), matching the Inbound Email API in full — including the custom-domain and catch-all support from the July 26 entry below. The CLI gains eight senderkit inbound * commands, and the MCP server eight matching tools; see the Tools reference for parameters.
• suppressed is now included in the SDK’s exported Message.status values (the status itself was introduced in the July 26 entry below).
• openedAt / clickedAt on Message — the fields the July 8 entry below described ship in this release.

​

Retry a failed send from the Logs page

​

opted_out now only reflects sends skipped before dispatch

• New message.complained webhook event, separate from message.opted_out. A spam complaint now fires both events; a plain unsubscribe fires message.opted_out alone.
• messages.list({ status: "opted_out" }) and the equivalent CLI/MCP status filters now match only pre-send suppressions, not post-delivery unsubscribes or complaints.
• See Messages → lifecycle for the updated status reference.

​

suppressed message status

​

Custom inbound domains and catch-all addresses

• Custom inbound domains — receive mail at addresses on your own domain (e.g. inbound.acme.com) instead of only the shared {slug}.in.senderkit.email. Claim a domain from the dashboard or POST /v1/inbound/domains, publish the DNS records it returns (an MX, plus a DKIM TXT proving ownership — skipped if the domain already has a verified sending domain, which reuses its identity), and a background sweep verifies it. New senderkit_inbound_domains_list / _create / _delete MCP tools mirror the REST surface.
• Catch-all addresses — create an address with localPart: "*" to receive mail sent to any local part on a domain that no exact address already claims. An exact-match address always takes priority over the catch-all.

​

Receive email, not just send it

• New Inbound dashboard page — create and remove addresses, optionally binding one to a specific webhook endpoint or a forwarding address.
• New /v1/inbound/* API routes — list/create/delete addresses, list and read received messages (parsed body, headers, SES spam/virus/SPF/DKIM verdicts), and fetch attachments or the original raw MIME source (30-day retention). Requires an API key with the new inbound scope.
• Plan-gated address caps — Free 1, Starter 10, Pro 50. A received live message counts against the same monthly message quota as outbound sends.

​

Style emails without touching HTML

• Fonts — independent heading and body fonts, picked from a curated set of web-safe and Google fonts, or a custom Google Font by name.
• Colors — page background, content background, and body, heading, and link text colors.
• Content width — the email’s maximum content width, 320–900px.

​

Resized images no longer squeeze on narrow screens

​

Bounce/complaint/delivery events fixed for identity-level SES notifications

​

Preheader now renders as the actual inbox preview snippet

​

cc, bcc, replyTo, and attachments now work on every connection type

​

Sender display names are now RFC-correct on every provider

​

Recipient reactivations are no longer treated as an opt-out

​

More reliable status updates on inbound provider events

​

Provider-reported opens and clicks on messages

• Message gains openedAt and clickedAt — ISO 8601 strings, or null until the event happens — returned by messages.get and messages.list.
• senderkit messages get prints both fields.
• Two new subscribable webhook events: message.opened and message.clicked. These are engagement signals only — they never change a message’s status (delivered stays the terminal state). The message.clicked payload additionally carries the clicked link.

​

Per-message From overrides, now identical on templated and raw sends

• from — From address override (bare address). Previously accepted on sendRaw() only; now also accepted on send().
• fromName — new on both — From display name override, rendered as Name <address>. Max 128 characters; no control characters or angle brackets.

• CLI: senderkit send and senderkit send-raw gain --from / --from-name.
• MCP: senderkit_send and senderkit_send_raw gain matching from / fromName inputs.

​

blockedReason removed from the SDK type

​

Inbound webhook retries are now deduplicated

​

Message preview in Logs

• Email — renders the HTML in a sandboxed iframe (no remote resources, tracking pixels, or external fonts load inside the preview).
• SMS / push / web-push — shows the message body as plain text.

​

blockedReason is operator-only

​

What still works

• messages.list({ status: "blocked" }) — filtering for blocked messages works as documented. Only blockedReason is withheld; every other message field is present.
• Message.status === "blocked" — detection and the status transition are unchanged.

​

Load older message history in Logs

• Scroll to load — as you scroll toward the bottom, the next 50 messages load automatically. A manual “Load older messages” button is available as a fallback.
• Live updates while reading back — when you’re scrolled away from the top, incoming live messages are buffered behind a ”↑ N new messages” pill instead of shifting the viewport. Returning to the top flushes the buffer and resumes the live tail.
• “Beginning of history” footer appears once all available records have loaded.
• The client-side text filter applies to all loaded messages combined.

​

blocked message status

​

What’s new

• blocked status — Message.status can now be "blocked". A blocked message was stopped by the abuse scanner before provider dispatch and will not be retried. The message timeline records a generic notice; detection details are operator-only (see the June 19 entry for clarification).
• messages.list({ status: "blocked" }) — the status filter now accepts "blocked" in the SDK, CLI (--status blocked), and MCP (senderkit_messages_list). Before this release, filtering by "blocked" was rejected as an invalid enum value.

​

Starter plan + pricing restructure

​

What changed

• Free — template cap raised from 5 → 10; message cap lowered from 3,000 → 500/month. The free tier is now scoped for evaluation and low-volume personal projects rather than production transactional mail.
• Starter ✨ new — $5/month: unlimited templates, 5,000 messages/month, and access to custom sending domains for DKIM alignment.
• Pro — now has an enforced 50,000 messages/month cap (was uncapped). Price and unlimited templates are unchanged.
• Custom sending domains are now available on any paid plan (Starter and Pro), not just Pro. See Channels → Custom sending domains.

​

Built-in email sender caps

​

Upgrading

​

Route Supabase auth emails through SenderKit

​

One-click setup

• Provisions a signed inbound webhook endpoint
• Seeds and publishes six curated auth templates (supabase-signup, supabase-magiclink, supabase-recovery, supabase-invite, supabase-email-change, supabase-reauthentication)
• Configures Supabase’s Send Email Hook to point at the endpoint

​

MCP tool manifest sync

• senderkit_send.to now explicitly covers all four channels: email address, E.164 phone number, push device token, and JSON-encoded web-push PushSubscription.
• senderkit_messages_list.status is now a strict enum in the tool schema (scheduled, queued, rendered, dispatched, sent, delivered, failed, opted_out, canceled), matching the API’s behavior of rejecting unknown statuses with 400. The CLI validates --status client-side and lists choices in --help.
• Template slugs are documented as always lowercase in the senderkit_send template parameter and senderkit_templates_get slug parameter. Slugs are canonicalized to lowercase on every write path (existing mixed-case slugs continue to resolve, but new slugs are created lowercase).

​

PHP SDK: senderkit/senderkit-php v0.2.0

• senderkit/senderkit-php — framework-agnostic core (PSR-18 HTTP client, PHP 8.1+).
• senderkit/senderkit-laravel — service provider, SenderKit facade, senderkit notification channel (all four channels), senderkit mail transport for existing Mailables, and VerifyWebhookSignature middleware.
• senderkit/senderkit-symfony — bundle with autowiring and a RequestVerifier webhook helper.

composer require senderkit/senderkit-php       # core
composer require senderkit/senderkit-laravel   # Laravel
composer require senderkit/senderkit-symfony   # Symfony

use SenderKit\Client;
use SenderKit\Request\TemplateSend;

$sk = new Client(apiKey: getenv('SENDERKIT_API_KEY'));
$result = $sk->send(new TemplateSend('welcome', 'user@example.com', ['name' => 'Ada']));
echo $result->id; // msg_…

​

Custom sending domains

• Add a domain in Dashboard → Channels → Add domain (Pro-gated; free workspaces see an upgrade prompt).
• Publish four DNS records: a white-label DKIM TXT record at senderkit._domainkey.{domain}, an MX + SPF pair on send.{domain} for the custom MAIL FROM, and optionally a root SPF and DMARC record. The dashboard shows the exact values to copy and probes DNS live once records are detected.
• SenderKit verifies the domain (polls every 5 minutes; Check now button for immediate re-check). Verification completes within minutes once records propagate; claims expire after 72 hours.
• Once verified, the domain activates as a managed connection in Channels. It can be set as the workspace default or targeted per template. The shared tx.senderkit.email sender stays as the implicit fallback.

await senderkit.sendRaw({
  channel: "email",
  to: "customer@example.com",
  from: "billing@acme.com",   // acme.com must be verified
  content: { subject: "Your invoice", html: "…" },
});

​

Least-privilege API key scopes

​

Scope model

​

TypeScript SDK (@senderkit/sdk v0.8.0)

import {
  SenderKitPermissionError,
  SenderKitAuthenticationError,
} from "@senderkit/sdk";

try {
  await senderkit.send(…);
} catch (err) {
  if (err instanceof SenderKitPermissionError) {
    // Key is valid but lacks the required scope
  } else if (err instanceof SenderKitAuthenticationError) {
    // Key is bad/missing/revoked
  }
}

​

CLI (@senderkit/cli v0.6.1)

​

senderkit mcp install now defaults to hosted OAuth

# Hosted OAuth config for every detected client (new default — no API key stored)
senderkit mcp install

# Hosted with API key bearer auth instead of OAuth
senderkit mcp install --api-key-auth

# Local stdio subprocess (previous default, now opt-in)
senderkit mcp install --local

​

Lean template and message reads (TemplateVersion.content removed)

​

What changed

• TemplateVersion.content is removed from the Template type. Code that accessed template.currentVersion.content will now produce a TypeScript compile error. The rest of currentVersion (versionNumber, variables, publishedAt) is unchanged.
• messages.list() and messages.get() also omit rendered content; vars, timeline, and metadata are still returned on every message.

​

AI-powered template creation via MCP

​

senderkit_templates_create

​

senderkit_templates_regenerate

​

senderkit_context tool + mode on send results

​

TypeScript SDK

​

CLI

senderkit context
# mode:     test
# livemode: false

​

MCP server

​

Workspace identity in context

​

TypeScript SDK

const ctx = await senderkit.context();
console.log(ctx.workspace.name); // "Acme Inc"
console.log(ctx.mode);           // "live"

​

CLI

senderkit context
# workspace: Acme Inc
# slug:      acme
# mode:      live

​

MCP server

​

Default URL corrections

​

TypeScript SDK

​

CLI

​

Web Push channel

​

TypeScript SDK

• Channel now includes "web-push".
• New RawWebPushContent type: { title, body, icon?, clickUrl?, badge?, data? }.
• sendRaw({ channel: "web-push", to, content }) — to is the JSON-encoded browser PushSubscription (endpoint + p256dh/auth keys). Your application collects these after the user grants browser permission.

​

CLI

• senderkit send-raw --channel web-push with --title, --body, --icon, --click-url, --badge, and --push-data flags.

​

MCP server

• senderkit_send_raw and senderkit_messages_list channel enums now accept "web-push". The icon and clickUrl inputs are available on senderkit_send_raw. Both the CLI stdio server and the app-hosted HTTP MCP server are updated.

​

Dashboard / API

​

CLI cc/bcc/attachments flags fixed

• --cc / --bcc — accept a comma-separated string (a@x.com,b@x.com) or a JSON array string ('["a@x.com","b@x.com"]').
• --attachments — accepts a JSON array string of attachment objects.

​

Initial public release

​

TypeScript SDK — @senderkit/sdk@0.2.0

• SenderKit client with send(), sendRaw(), and sendBatch() for multi-channel delivery (email, SMS, push).
• messages.list() (with metadata filtering), messages.get(id), and messages.cancel(id).
• templates.list() and templates.get(slug).
• scheduledAt on send / sendRaw for scheduled delivery.
• client.mode ("live" / "test"), derived from the API key prefix; the client validates that keys start with sk_live_ or sk_test_ at construction.
• Typed error hierarchy: SenderKitApiError, SenderKitAuthenticationError, SenderKitValidationError, SenderKitRateLimitError, SenderKitTimeoutError, and SenderKitNetworkError.

​

CLI — @senderkit/cli@0.2.0

• senderkit login for interactive authentication (API key input is hidden).
• senderkit send and senderkit send-raw.
• senderkit templates list / get.
• senderkit messages list / get / cancel.
• --json flag for structured, machine-readable output (including errors).

​

MCP server — bundled in @senderkit/cli@0.2.0

• senderkit_send and senderkit_send_raw
• senderkit_templates_list and senderkit_templates_get
• senderkit_messages_list, senderkit_messages_get, and senderkit_cancel_message