Email

Resend with Claude & ChatGPT—Resend MCP server

Send transactional and broadcast email enriched with the customer’s full context, and build segments from the unified profile, through one MCP. Works in Claude, ChatGPT, Cursor, and any MCP-compatible agent.

What it looks like

What does Resend look like in Claude?

Connect Resend once. Your agent builds segments from the unified profile and sends context-rich email—through one MCP server, identity-resolved with your CRM, support, and website events.

MCP

Resend, exposed as MCP tools.

Claude · pathbound MCP connected
you
Email the trial users who activated but went quiet, referencing what they did.
↳ list_contacts { lifecycle: "trial", event: "activation", quiet_days: 14 } 9 contacts · 430ms
segment 9 activated, silent 14d+
context per-contact: feature used, last touch
↳ batch_get_activity { contact_ids: […9], events_limit: 10 } 9 timelines · 380ms
used one feature each, then nothing for 14d+
claude
Found 9 trial users who activated then went quiet, and wrote a note to each referencing the feature they actually used. Want me to send them through Resend?
review Nothing is sent yet: the notes are in the chat. Each goes out only when the agent calls resend_send_email, a tool a workspace admin has to turn on.
claude_desktop_config.json
{
  "mcpServers": {
    "pathbound": {
      "url": "https://mcp.pathbound.ai/mcp"
    }
  }
}
Resend tools out of the box · read & write
get_contact — unified profile to ground the message
resend_send_email — send one email to a contact, written from full context
resend_create_segment — build a segment from the unified profile
resend_add_contacts_to_segment — target the right contacts dynamically
list_contacts — find the audience by lifecycle, source, or behavior
create_contact_note — log the outreach on the contact timeline

…plus many more—more than 100 MCP tools in total, across contacts, companies, deals, events, and conversations.

Setup

How do I connect Resend to Claude?

Paste an API key. Drop a snippet into your MCP client. Ask a question.

  1. 01

    Sign up for Pathbound

    Create an account at pathbound.ai. Every plan starts with 14 days free, no card.

  2. 02

    Connect Resend

    In the dashboard, go to Integrations → Resend → Connect. Paste your Resend API key. Pathbound can then send on your behalf and manage segments built from the unified profile, once a workspace admin turns those tools on under MCP Tools; each is off by default.

  3. 03

    Add Pathbound to your MCP client

    Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Customize → Connectors → Add custom connector → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.

    claude_desktop_config.json
    {
      "mcpServers": {
        "pathbound": {
          "url": "https://mcp.pathbound.ai/mcp"
        }
      }
    }
  4. 04

    Run a test prompt

    Ask the agent: “Draft a re-engagement email for [email protected] based on her activity.” The agent reads the profile and writes the email in the chat. Nothing is sent until it calls resend_send_email.

Why Pathbound

Most email tools blast a list. Yours can write to the one customer who matters.

A direct Resend connector gives your agent a send endpoint. Pathbound gives it the customer—so every email is grounded in the contact’s CRM stage, support history, and product behavior, and every segment is built from the live unified profile, all over the Model Context Protocol.

Send from full context

Agents draft and send via resend_send_email, grounded in the customer’s entire history—not a merge-tag template. The send is logged back on the contact’s timeline.

Segments from the graph

Build and target segments from the unified profile—“trial users who activated but went quiet”—with resend_create_segment and add/remove tools. Live segments, not a static CSV.

One profile, every channel

The same unified contact powers Resend sends, CRM updates, and support context. Connect once; every agent and channel reads and writes the same record.

Built for LLMs

Token-efficient profiles in, governed sends out. The agent gets the context it needs to write well, not a raw contact dump.

FAQ

Common questions.

Is this an official Resend MCP server?

Pathbound is an independent platform. We connect to Resend via its official API using a key you provide, and expose it through one Model Context Protocol server alongside your other sources. Not affiliated with Resend.

Can the agent send email, or just read?

Send. resend_send_email sends one email to one contact, written from full customer context; resend_create_broadcast prepares an email to a whole segment without sending it, and resend_send_broadcast sends it. The segment tools build audiences from the unified profile. Each of these tools is off until a workspace admin turns it on.

How do segments work?

Segments are built and managed through the MCP tools from your live unified profile (e.g. “activated trial users, silent 14 days”), so they reflect current data on every send rather than a stale exported list.

Which MCP clients does this work with?

Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.

Is my customer data secure?

Tenant-isolated and OAuth-scoped per user, with connection credentials encrypted at the application layer. Pathbound does not sell customer data, and we don’t call AI providers on your behalf—your MCP client does, under your account and the AI provider’s terms.

What about Gmail, HubSpot, Apollo?

Same MCP server, same tools—just connect a different source. See the integrations directory.

Try it on your own data

Within five minutes, your agent is querying real customer context.

Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.