Resend

The connector works with your organisation's own Resend account and one API key. The key serves two jobs: it keeps the contact list your Broadcasts go to up to date, and it sends email from a domain you verified at Resend. The tools that manage contacts never send anything, and no Broadcast is created or sent from here.

Does Resend have an MCP?

Yes. Resend hosts its own at https://mcp.resend.com/mcp, with nothing to install. Sign-in is OAuth in the browser, or an API key passed as a bearer token for headless use. Its documentation lists tool groups for emails, received emails, templates, contacts, broadcasts, automations, events, domains, segments, topics, API keys, webhooks and logs, so it can send, read inbound mail and change most resources, including domains and keys. Tulina's connector is the narrower route, held in the same MCP link as the rest of your tools.

How do you connect Resend to Claude and ChatGPT?

Through Tulina's MCP server, in three steps:

1. In Resend, create an API key at resend.com/api-keys with the Full access permission. A Sending access key still sends, but Resend refuses it on contacts, segments and topics, and the tools say so.
2. Paste the key into Tulina's Resend connector as an organisation admin. It is stored in the vault and never shown to the model. There is no platform key, so the key is always your organisation's.
3. Add https://mcp.tulina.ai/mcp to Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.

Sender addresses are declared in the organisation's email settings. Each one sends either through Resend or through Tulina's other mailer, so check which one the address you want uses.

Tulina vs Resend's official MCP server

Resend's server covers the whole platform. Tulina's covers the audience, and sending from a declared address.

If the model should build Broadcasts, manage domains or read inbound mail, Resend's own server is the better choice. Tulina fits when the audience or a single send is one step in a longer piece of work, such as a signup that also reaches your CRM.

What you can ask it

"Add these people to the newsletter segment, but show me what would change first." The agent runs the upsert as a dry run, reports what it would create and update, and writes only after you agree. One call takes up to 50 contacts and returns a receipt.

"Who unsubscribed from the newsletter?" The agent lists the segment's contacts filtered to unsubscribed ones. It scans up to 1,000 contacts itself and returns a cursor when there are more.

"Marie asked to stop receiving the newsletter." The agent updates her contact to unsubscribed. It does not delete her, because deleting also drops the opt-out and a later import would make her mailable again.

Resend pairs with Brevo when a team keeps newsletter and transactional mail in different tools, and with Gmail for one-to-one mail from your own mailbox.

What the Resend connector can't do

• It does not create, edit or send a Broadcast, and it does not manage templates or automations.
• It does not manage domains, API keys or webhooks, or read logs and inbound mail.
• An upsert never resubscribes someone who unsubscribed. They are listed as kept unsubscribed, and resubscribing is an explicit update on the person's own request.
• Topics are read-only. A recipient changes their own topic subscriptions from the unsubscribe page.
• Segments can be created but not deleted here. Deleting one happens in the Resend dashboard.
• Contacts, segments and topics need a Full access key. A sending-only key is refused.
• A send under your own organisation's key carries the platform's footer unless the organisation has declared its own unsubscribe.