← Back to all sparks
R

Resend

INFRA · APIS
Velocity6.3

Email API for developers to send transactional and marketing email

Resend is wiring itself into every agent runtime it can reach, one standard at a time

agent-integrationsmcpoauthdeveloper-experienceemail-apideliverability
Current state
Almost every recent entry is about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and now support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor — but it is the smaller half of the feed. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
Where it's heading
Resend is treating agents as the next class of sending client and building the authorization and discovery plumbing they need before that traffic arrives. The progression is legible: first authenticate third parties (OAuth), then be callable (MCP), then be installable per vendor (Codex, Claude), and now be installable by standard. The developer-experience work — secret scanning, email-client compatibility warnings, Message-ID threading — keeps the human-facing product credible while that shift happens.
Prediction
Having covered authorization and discovery, the gap left is what an agent is permitted to send once connected; scoped, per-agent sending limits or approval controls are the natural next piece.

Recent moves

  1. 6d ago

    Agent Plugin Support

    ⚡ SPARK

    Resend now supports the Agent Plugins Standard, which turns a series of one-off vendor integrations into a single interface any conforming agent client can install. It is the endpoint of the arc the last two months have been building — OAuth, then MCP, then per-vendor plugins, now a standard.

    View source ↗
  2. 7d ago

    Email Compatibility Checker

    The code editor now warns when pasted HTML looks likely to break in email clients. A small guardrail against the oldest failure in the category, and consistent with the pattern of catching problems before a send rather than reporting them afterward.

    View source ↗
  3. 13d ago

    Remote MCP Supports the 2026-07-28 Spec

    The remote MCP server moves to the 2026-07-28 spec and its stateless protocol, which removes session state as a scaling constraint for agent callers. Keeping current with the spec is what makes the broader agent-integration push credible.

    View source ↗
  4. 16d ago

    Template Folders

    Templates can now be organized into folders. Straightforward organizational work for accounts that have accumulated enough templates for the flat list to hurt.

    View source ↗
  5. 22d ago

    Email Suppressions

    Suppressed addresses are now manageable from both the dashboard and the API, giving teams direct control over a list that governs deliverability. Exposing it through the API matters more than the dashboard view, since it is what lets suppression be handled programmatically.

    View source ↗
  6. 28d ago

    Resend Plugin for Codex

    The MCP server and Resend's skills become installable from the official Codex plugin marketplace. One more per-vendor distribution point, and in hindsight a step toward the standards-based approach that followed.

    View source ↗