Set up Resend MCP Server

Setting up the official Resend MCP Server as a hosted remote service or locally via npx for AI clients such as Claude Code.

Published on 18.09.2026

What the Resend MCP Server is

The Resend MCP Server connects AI assistants to the Resend email platform via the Model Context Protocol, or MCP. MCP is an open standard that lets AI applications such as Claude, Cursor, or Claude Code access external tools and services in a structured way without building a custom integration for every application. According to the provider, the server lets you send and receive emails, manage contacts, create broadcasts, and administer domains directly from any MCP-capable client. Resend offers two variants for this: a remote server hosted by Resend itself, and the underlying open-source local server, available as a standalone package on npm, which can alternatively be self-hosted.

The hosted remote server

The easiest entry point is the server Resend hosts at a fixed address. Since no local process needs to run, this option works particularly well for web-based clients and hosted agent platforms. When connecting, the client opens a browser window where you log in to Resend and approve access via OAuth. For environments without a browser, such as servers or automated pipelines, a Resend API key can instead be set as a Bearer token in the authorization header. According to the provider's documentation, common clients including Claude Code, Claude itself, Cursor, Codex, GitHub Copilot in VS Code, Windsurf, and Warp are directly supported, each with its own configuration schema for establishing the connection.

The local server as an alternative

Anyone who prefers to run the server themselves, for example for privacy or control reasons, can start the local server via npx without a permanent install. The local server supports two transport modes: standard input/output as the default, and HTTP as an alternative. Running it requires a Resend API key generated in your own Resend account, plus a verified sending domain, since Resend only reliably delivers mail through verified domains. Configuration for most clients is a simple JSON structure containing the start command and the environment variable holding the API key. The local server is open source and also forms the technical foundation of the hosted offering, so functionality and behavior are largely identical between the two variants.

Setting it up in practice

For Claude Code, the remote server can be added as an HTTP transport with a single command, after which you complete the login through Claude Code's internal MCP command. For other clients, you enter the server address, or for the local server the start command and the API key, into that client's respective configuration file. Once connected, the AI assistant has the Resend tools available, so email sending, contact management, and domain administration can be driven directly from natural-language instructions without writing API calls yourself.

Security and limits

Because the server can actually send emails and modify account data, it is a tool with real external effects. An API key should therefore be treated like any other secret: not stored in plain text in shared configuration files or chat logs, and scoped as narrowly as possible if Resend offers such a restriction. With the OAuth variant, access control sits with Resend's own login system; with the API-key variant, responsibility for handling the key securely lies with whoever operates that environment. Especially in automated or multi-step agent workflows, it is worth manually confirming critical actions such as an actual send to a large recipient list before execution, to avoid misfired sends caused by misinterpreted instructions.

Who benefits from using it

Development teams that already use Resend as their sending infrastructure benefit the most, since recurring email tasks like transactional messages, status lookups, or domain maintenance can be integrated directly into an AI-assisted development workflow. For projects without an existing Resend account, adopting it only makes sense if you already plan to use Resend as your sending service, since the MCP server itself does not provide standalone mail delivery without a Resend account.

Published on 18.09.2026

Categories

Frequently asked questions

Why are there product and repository links?

The product link points to the provider's official documentation. The repository verifies source code, licence, setup details, and the exact GitHub star count.

Are GitHub stars a rating?

No. The number is a point-in-time snapshot collected through the GitHub API on 2026-09-08 and does not replace security or quality review.

How do I start without unnecessary risk?

Start with harmless actions like listing domains or retrieving sent emails. Store API keys in environment variables and enable email sending operations only after review.