Resent

io.github.resentmailPublished by GitHub account resentmailv1.0.0Updated Oct 24, 2026

Transactional email for AI agents: templates, domain verify, and sends.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Resent is a remote MCP server that lets an AI assistant send transactional email, manage templates and verify sending domains.

What you can do
Send transactional email on behalf of the user or application, as described in the registry entry. Manage email templates used for those sends. Verify sending domains so mail can be delivered from them. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant needs to trigger transactional email such as notifications or confirmations, or to set up templates and sending domains for an application. Less relevant if you only need to read or organize received mail.
Requirements
A remote MCP endpoint at resent.one reached over streamable HTTP. OAuth authentication is required, so the user must sign in and authorize access. No environment variables or headers are declared.
Before you install
The server can send email and change templates and domain settings, which are outward-facing actions. OAuth grants access to the connected account, so review the scopes requested. Sending mail may incur costs or affect sender reputation depending on the provider's terms.

Installation

In SourceWeft

  1. Open Resent in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.resentmail%2Fresent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "resent": {
      "type": "http",
      "url": "https://resent.one/api/v1/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.