What an agent can do in Resend
Send and manage email with Resend: emails, templates, contacts, broadcasts, automations, domains, segments, webhooks and logs.
Jobs on Rush that use Resend
- Draft a Product Update Email in Resend From a Changelog
- Check Email Deliverability in Resend
- Send a Personal Welcome Email for Each Signup Through an API
Code changes on a Resend codebase
These change the code of an app built on Resend. They run on your repository in a Project and need no Resend connection.
How Resend connects
Resend is a remote MCP server, published by Resend, at https://mcp.resend.com/mcp. Connecting it signs in through the MCP OAuth flow on Resend's side.
From Resend: Resend's MCP documentation.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names resend in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Resend",
"url": "https://mcp.resend.com/mcp"
}Whose Resend account the agent uses
Your Resend connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Resend, and a run started with an API key uses the Resend of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Resend, and that agent's runs use their account and nothing else: never yours, never another user's.
More Marketing integrations
Frequently asked questions
How do I connect Resend to Rush?
Open Settings → Connections in the console and connect Resend, or send POST /me/connections with {"type":"mcp","name":"Resend","url":"https://mcp.resend.com/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Resend account?
No. A run gets your Resend connection only when it names it in connections ("connections": ["resend"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Resend?
Send and manage email with Resend: emails, templates, contacts, broadcasts, automations, domains, segments, webhooks and logs. 3 published jobs use it; this page lists them.
Can my app's users connect their own Resend?
Yes. Make each user an agent from your template, and they sign in to their own Resend through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for marketing teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to