Connect Resend to Claude Code

Send transactional email and manage domains, contacts and broadcasts. Add Toolspoke to Claude Code once and it can use 11 Resend actions. Your Resend credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Resend and connect it

    Add Resend to a project in your Toolspoke workspace.

    API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    API key
    Dashboard → API Keys → Create API Key. A key with Sending access covers send_email; the domain, contact and broadcast reads need Full access, and so do create_contact and delete_contact.
  3. Choose what Claude Code may do

    All 11 actions start on. Switch off any of the 3 actions that change something in Resend, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Resend actions that only read, so they are safe to try first.

  • Retrieve one sent email by id, with its delivery status, recipients and the body that was sent
  • List the sending domains on this account with their verification status and region
  • Retrieve one sending domain by id, including the DNS records Resend expects and whether each one is verified
  • List the API keys on this account by name, id and creation date

What Claude Code can do in Resend

8 actions read, one writes and 2 delete or permanently change something.

Reads

  • Get email

    Retrieve one sent email by id, with its delivery status, recipients and the body that was sent.

  • List domains

    List the sending domains on this account with their verification status and region. Takes no arguments and costs nothing, which is why it is what an install tests itself with, and it is also the answer to "why was that send rejected", which is usually an unverified domain.

  • Get domain

    Retrieve one sending domain by id, including the DNS records Resend expects and whether each one is verified.

  • List api keys

    List the API keys on this account by name, id and creation date. Resend never returns a key's secret after it is created, so this shows which keys exist rather than their values.

  • List audiences

    List the audiences on this account. Resend has superseded audiences with segments and marks these endpoints deprecated, so treat this as a way to read what already exists rather than the shape to build new work on.

  • List contacts

    List contacts on this account, optionally narrowed to one segment. Contacts are top-level in the current API, there is no audience id in this path.

  • Get contact

    Retrieve one contact. The identifier may be the contact id or the email address itself. Resend accepts either in this path segment.

  • List broadcasts

    List broadcasts on this account with their status and send times. Reading a broadcast never sends one, this connector exposes no operation that sends a broadcast at all.

Writes

  • Create contact

    Add a contact. This is a write rather than destructive: it sends nothing and delete_contact undoes it. It does decide who a later broadcast reaches, so treat consent as the caller's responsibility. Only email is required.

Deletes or permanently changes

  • Send email

    Send one email. Classified destructive rather than write, and deliberately so: it delivers to real inboxes, it cannot be recalled once accepted, and Resend bills per send. A write grant can add and read contacts here and send nothing. Supply html, text, or both; from must be an address on a domain this account has verified. Returns the message id, which is what get_email later takes.

  • Delete contact

    Remove a contact from this account permanently. Destructive because there is no undo and nothing recoverable behind it: the record and its segment memberships go, and re-adding the address does not restore what was there. The identifier may be the contact id or the email address.

Resend in Claude Code: questions

Does Claude Code see my Resend credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Resend?

Yes. Each of the 11 actions can be switched off for a project. Turn off the 3 that change something and Claude Code can only read.

Will 11 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Resend action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Resend call does not run in a sandbox, so it bills nothing.

Try Resend in Claude Code

Free to start, and tool calls cost nothing on any plan.