Resend MCP | Resend email connector for AI agents

Tools your messaging agent reaches for on Resend MCP, scoped per user.

CALL ANY TOOL

Send transactional email and broadcasts, manage domains, audiences, contacts, and templates through Resend's official MCP server.

resendmcp_add_contact_to_segment

Add contact to segment

Add a contact to a segment in Resend (by contact ID or email).

Parameters

Name

Type

Required

Description

segmentId

string

Required

Segment ID to add the contact to

contactId

string

Optional

Contact ID

string

Optional

Contact email address

resendmcp_batch_remove_suppressions

Batch remove suppressions

resendmcp_cancel_broadcast

Cancel broadcast

resendmcp_compose_broadcast

Compose broadcast

resendmcp_create_api_key

Create api key

resendmcp_create_contact

Create contact

resendmcp_create_domain

Create domain

resendmcp_create_template

Create template

Create a new email template in Resend. Templates are created in draft status. Use publish-template to make them available for sending. Variables use triple-brace syntax in HTML: {{{VAR_NAME}}}. **Workflow:** create-template → get-tiptap-json-content (with include_schema: true) → compose-template → publish-template. **Content options after creating:** - **compose-template** (recommended): Sets TipTap content that the user can visually edit in the Resend dashboard. Use this when the user wants to collaborate on or refine the template in the editor. - **update-template with html/text**: Sets static HTML/text content. Use this only when the user explicitly wants to set raw HTML. Switching between compose and html/text modes is lossy: some content or formatting may be lost. Ask the user before switching.

Parameters

Name

Type

Required

Description

html

string

Required

The HTML content of the template. Use triple-brace syntax for variables: {{{VARIABLE_NAME}}}. Email HTML requirements: follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td>: never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="..."): no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only: no relative paths - Always include alt text LINKS & BUTTONS - Never use <button>: use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">

name

string

Required

The name of the template.

alias

string

Optional

An alias for the template. Can be used instead of the ID to reference the template.

from

string

Optional

Sender email address (e.g., "Your Name <sender@example.com>"). Can be overridden when sending.

replyTo

string

Optional

Default Reply-to email address(es). Can be overridden when sending.

subject

string

Optional

Default email subject. Can be overridden when sending.

text

string

Optional

Plain text version of the message. If not provided, HTML will be used to generate it.

variables

array

Optional

Array of template variables (up to 50 per template).

resendmcp_disconnect_from_editor

Disconnect from editor

resendmcp_get_automation

Get automation

resendmcp_get_contact

Get contact

resendmcp_get_domain

Get domain

resendmcp_get_log

Log get

resendmcp_get_segment

Get segment

resendmcp_get_template

Get template

resendmcp_list_api_keys

List api keys

resendmcp_list_contact_properties

List contact properties

resendmcp_list_domains

List domains

resendmcp_list_received_email_attachments

List received email attachments

resendmcp_list_suppressions

List suppressions

resendmcp_manage_events

Manage events

resendmcp_publish_template

Publish template

resendmcp_remove_broadcast

Remove broadcast

resendmcp_remove_contact_property

Remove contact property

resendmcp_remove_suppression

Remove suppression

resendmcp_send_batch_emails

Send batch emails

resendmcp_update_api_key

Update api key

resendmcp_update_broadcast

Update broadcast

Update broadcast metadata by ID or Resend dashboard URL (name, subject, from, html, text, segment, preview text, reply-to). To edit TipTap content, use compose-broadcast instead. **Important:** The API requires `from` and `segmentId` to be set on the broadcast. If the broadcast was created from the dashboard, these may be empty. Always call get-broadcast first to check, and include `from` and `segmentId` in your update if they are not already set. Use list-domains to find verified domains for the from address, and list-segments to find segment IDs. **Note on html/text fields:** Setting html or text via this tool replaces any content previously set via compose-broadcast. This switch is lossy: some content or formatting may be lost. Prefer compose-broadcast for content changes. If the broadcast was composed with TipTap content, ask the user before overwriting it with raw HTML.

Parameters

Name

Type

Required

Description

broadcastId

string

Required

Broadcast ID or Resend dashboard URL (e.g. https://resend.com/broadcasts/<id>)

from

string

Optional

From email address (e.g. "onboarding@resend.com" or "Resend <onboarding@resend.com>")

html

string

Optional

HTML content of the email. Email HTML requirements: follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td>: never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="..."): no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only: no relative paths - Always include alt text LINKS & BUTTONS - Never use <button>: use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">

name

string

Optional

Name for the broadcast

previewText

string

Optional

Preview text for the email

replyTo

array

Optional

Reply-to email address(es)

segmentId

string

Optional

Segment ID to send to

subject

string

Optional

Email subject

text

string

Optional

Plain text content of the email

resendmcp_update_contact_topics

Update contact topics

resendmcp_update_template

Update template

Update template metadata by ID, alias, or Resend dashboard URL (name, subject, from, html, variables, etc.). After updating a published template, use publish-template again to make the changes live. To edit TipTap content, use compose-template instead. **Note on html/text fields:** Setting html or text via this tool replaces any content previously set via compose-template. This switch is lossy: some content or formatting may be lost. Prefer compose-template for content changes. If the template was composed with TipTap content, ask the user before overwriting it with raw HTML.

Parameters

Name

Type

Required

Description

string

Required

The template ID, alias, or Resend dashboard URL (e.g. https://resend.com/templates/<id>)

alias

string

Optional

New alias for the template.

from

string

Optional

New sender email address.

html

string

Optional

New HTML content for the template. Email HTML requirements: follow all of these without exception: STRUCTURE - Always include <!DOCTYPE html>, <html>, <head>, <body> - Layout must be table-based: <table>, <tr>, <td>: never use <div> for layout - Outer wrapper table at width="100%", inner content table at max 600px wide - Every table must have cellpadding="0" cellspacing="0" border="0" CSS - All styles must be inline (style="..."): no <style> tag, no external stylesheets - No flexbox, no grid, no CSS variables, no CSS shorthand (use padding-top not padding) - font-family must always include web-safe fallbacks (Arial, Helvetica, Georgia, sans-serif) - Always set font-size, line-height, and color explicitly on every text element IMAGES - Always set width, height, border="0", display:block on every <img> - Use absolute URLs only: no relative paths - Always include alt text LINKS & BUTTONS - Never use <button>: use <a> styled as a button inside a <td> - No <video>, <form>, or <input> elements - No JavaScript of any kind OUTLOOK COMPATIBILITY - Use bgcolor attribute on <td> alongside CSS background-color - No CSS background-image (poor Outlook support) - Add <!--[if mso]> conditionals where needed for Outlook rendering META (in <head>) - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <meta http-equiv="X-UA-Compatible" content="IE=edge">

name

string

Optional

New name for the template.

replyTo

string

Optional

New Reply-to email address(es).

subject

string

Optional

New default email subject.

text

string

Optional

New plain text version of the message.

variables

array

Optional

New array of template variables (replaces existing variables).

For more tools, view docs.

Build your Agent

Drop the toolkit in, point it at the user, and your messaging agent can use Resend from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Resend MCP tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["resendmcp"], toolNames: [
    "resendmcp_add_contact_to_segment",
    "resendmcp_add_suppression",
    "resendmcp_batch_add_suppressions"
  ] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Did the invoice email to acme.com deliver?" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Resend MCP tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["resendmcp"], toolNames: [
    "resendmcp_add_contact_to_segment",
    "resendmcp_add_suppression",
    "resendmcp_batch_add_suppressions"
  ] },
  pageSize: 100,
});

const openai = new OpenAI();
const res = await openai.responses.create({
  model: "gpt-5",
  tools: tools.map((t) => t.openai),
  input: "Did the invoice email to acme.com deliver?",
});

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Resend MCP tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["resendmcp"], toolNames: [
    "resendmcp_add_contact_to_segment",
    "resendmcp_add_suppression",
    "resendmcp_batch_add_suppressions"
  ] },
  pageSize: 100,
});

const anthropic = new Anthropic();
const msg = await anthropic.messages.create({
  model: "claude-opus-4-6",
  max_tokens: 1024,
  tools: tools.map((t) => t.anthropic),
  messages: [{ role: "user", content: "Did the invoice email to acme.com deliver?" }],
});

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Resend MCP tools, scoped to the signed-in user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["resendmcp"], toolNames: [
    "resendmcp_add_contact_to_segment",
    "resendmcp_add_suppression",
    "resendmcp_batch_add_suppressions"
  ] },
  pageSize: 100,
});

const agent = new Agent({
  name: "resendmcp_agent",
  model: "gemini-2.5-pro",
  instruction: "Act as the messaging agent for the signed-in user.",
  tools,
});
await agent.run("Did the invoice email to acme.com deliver?");

Try these prompts

Paste any prompt into your agent to start using Resend.

Delivery checks

Copy the prompt

Copied

Did the invoice email to acme.com deliver?

Copy the prompt

Copied

List emails that bounced in the last 24 hours.

Copy the prompt

Copied

Show the sending domains and their verification status.

Sending

Copy the prompt

Copied

Send the onboarding email to the new signups audience.

Copy the prompt

Copied

Schedule the release broadcast for Thursday 9am.

Copy the prompt

Copied

Send a test of the password reset template to me.

Audience upkeep

Copy the prompt

Copied

How many contacts are in the product updates audience?

Copy the prompt

Copied

Remove unsubscribed contacts from the newsletter audience.

Copy the prompt

Copied

Which broadcast had the highest open rate last month?

SEE HOW AUTH WORKS

Users authorize Resend once. Their credentials stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Resend MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Resend MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Resend MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Resend MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Same per-user auth pattern across other agents and MCP connectors. Working code, live demos, fork what fits.

Support and Ops Teams

Email-to-calendar agent

Reads scheduling intent out of Gmail threads, resolves the times everyone actually has free, and creates the event on the user's own Google Calendar. No shared service account.

Gmail

Google Calendar

View agent

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Resend today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Resend as the user or as a shared key?

As the user. Each member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Resend bearer token credential stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Resend?

Yes. Pass a tool name filter to listScopedTools so the messaging agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Resend.

What happens when a user revokes Resend access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent send from a domain we have not verified?

No. Resend rejects sends from unverified domains, and the connector surfaces that error rather than silently retrying. Domain verification stays a human step in your Resend dashboard, which is where it belongs.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit