Skip to main content Announcing Tool Gateway MCP: the universal MCP Read the announcement
Live 38 Actions

Resend MCP Server
for AI Agents

Connect your AI agent to StackOne's Resend MCP server and give it 38 MCP tools out of the box. Auth, tool execution, and security all managed.

Resend logo
Resend MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

38 Agent Actions

Create, read, update, and delete across Resend — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Resend MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Resend tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Resend call.

Tools Discovery →

What is the Resend MCP Server?

A Resend MCP server lets AI agents read and write Resend data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Resend MCP server ships with 38 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Resend MCP Tools

Every action from Resend's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

API Keys

  • Create API Key

    Create an API key with an optional permission tier and domain restriction; the token is returned only once.

  • List API Keys

    List all API keys for the account.

  • Update API Key

    Rename an existing API key.

  • Delete API Key

    Permanently delete an API key so it can no longer authenticate requests.

Broadcasts

  • Create Broadcast

    Create a broadcast email targeted at a segment, optionally sending it immediately.

  • Send Broadcast

    Send or schedule an existing broadcast.

  • Retrieve Broadcast

    Retrieve a single broadcast by its id.

  • List Broadcasts

    List all broadcasts in the account.

  • Update Broadcast

    Update an existing broadcast.

  • Delete Broadcast

    Permanently delete a broadcast that has not been sent.

Contacts

  • Create Contact

    Add a contact with optional name, custom properties, segment membership and topic subscriptions.

  • Retrieve Contact

    Retrieve a single contact by id or email address.

  • List Contacts

    List contacts, optionally filtered by segment.

  • Update Contact

    Update an existing contact by id or email address.

  • Delete Contact

    Remove a contact from the audience by id or email address.

Domains

  • Create Domain

    Add a new sending domain and receive the DNS records needed to verify it.

  • Retrieve Domain

    Retrieve a single domain by its id.

  • List Domains

    List all domains in the account.

  • Update Domain

    Update a domain's tracking and TLS settings.

  • Delete Domain

    Remove a domain so it can no longer be used to send email.

Verify Domains

  • Verify Domain

    Trigger DNS verification for a domain.

Emails

  • Send Email

    Send a single email through Resend.

  • Send Batch Emails

    Send up to 100 emails in a single batch request.

  • Retrieve Email

    Retrieve a single sent email by its id.

  • List Emails

    List sent emails for the account.

  • Update Email

    Update a scheduled email, such as its send time.

Cancel Emails

  • Cancel Email

    Cancel a scheduled email that has not yet been sent.

Segments

  • Create Segment

    Create a segment used to group contacts for broadcasts.

  • Retrieve Segment

    Retrieve a single segment by its id.

  • List Segments

    List all segments in the account.

  • Update Segment

    Rename an existing segment.

  • Delete Segment

    Permanently delete a segment from the account.

Suppressions

  • Add Suppression

    Add a single email address to the suppression list to stop future sends.

  • Add Batch Suppressions

    Add multiple email addresses to the suppression list in one request.

  • Retrieve Suppression

    Retrieve a single suppression by its id.

  • List Suppressions

    List all suppressed email addresses.

  • Remove Suppression

    Remove a single suppression by its id.

  • Remove Batch Suppressions

    Remove multiple suppressions in one request.

Resend AI Agent Use Cases

Connect your AI agent to Resend and help your team scale the marketing operations they run by hand today.

Lead Nurture Sequences

Use StackOne to connect your AI agent to your marketing automation, CRM, and email tools to automate lead nurture email sequences.

View
HubSpotSalesforceActiveCampaignKlaviyoSendGridMailchimpLemlistGmail
Campaign Performance Reports

Use StackOne to connect your AI agent to your marketing automation, email, and analytics platforms to automate campaign performance reporting.

View
HubSpotMailchimpActiveCampaignKlaviyoSalesforceBrazeSendGridMarketo
Content Repurposing

Use StackOne to connect your AI agent to your document stores, email platforms, and messaging tools to automate content repurposing and distribution.

View
Google DriveConfluenceNotionMailchimpSendGridSlackGmailMicrosoft Teams

Set Up Your Resend MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Resend in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Check More marketing MCP Servers

Resend MCP Server FAQ

Does StackOne have a Resend MCP server?
Yes. StackOne offers a hosted Resend MCP server with 38 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Resend MCP server vs direct API integration — what's the difference?
A Resend MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Resend. A Resend MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Resend at runtime. StackOne provides both.
How does Resend authentication work for AI agents?
Resend authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Resend account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Resend MCP tools vulnerable to prompt injection?
Yes — Resend MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Resend agent and how do I avoid it?
Context bloat happens when Resend tool schemas and API responses eat your Resend agent's memory, preventing it from reasoning effectively. A single Resend query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Resend agent can access?
Yes — you can limit which actions your Resend agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Resend MCP server?
Yes — you can create custom agent actions for your Resend MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Resend's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Resend MCP server?
Skip a Resend MCP server if your integration is purely software-to-software — direct Resend API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Resend actions at runtime.
What AI frameworks and AI clients does the StackOne Resend MCP server support?
The StackOne Resend MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.