Resend Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.1.0Updated Oct 26, 2026

Query the Resend API (key; set RESEND_API_KEY, Bearer): domains, domain details, email details.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Server details

Identifier: io.github.mrfentmen/resend-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 17, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mrfentmen for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mrfentmen%2Fresend-mcp.svg)](https://sourceweft.com/mcp/io.github.mrfentmen%2Fresend-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant query the Resend email API for domains, domain details and email details using a Resend API key.

What you can do: List and inspect sending domains in the Resend account
Read details of a specific domain
Look up details of a specific email
All access goes through the Resend API with a Bearer API key
When to use it: Useful when you want an assistant to check Resend domain configuration or look up email records while working on transactional email setup, without leaving the chat.
Requirements: Runs as a local stdio process installed from the npm package @mrfentmen/resend-mcp (Node.js). Needs a Resend API key supplied as the RESEND_API_KEY environment variable; network access to the Resend API.

Before you install

Requires a Resend API key, which grants access to your Resend account data; keep it out of shared configs and logs. The description only mentions read-style queries, but the key's permissions determine what the server can reach.

Installation

In SourceWeft

Open Resend Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.0LatestOct 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.