Sadasend

io.github.SadaSendPublished by GitHub account SadaSendv1.0.0Updated Oct 27, 2026

Transactional email API & AI agent safety runtime with 12 scoped tools and SpendGuard.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for Sadasend, a transactional email API with an AI agent safety runtime offering 12 scoped tools and SpendGuard.

What you can do
  • Send transactional email through the Sadasend API from an assistant.
  • Work within a set of 12 scoped tools that limit what the agent can do.
  • Operate under SpendGuard, a safety runtime intended to constrain agent spending.
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in.
When to use it
Consider it when you want an assistant to send transactional email through Sadasend, or when you need agent actions to run under a scoped, spend-limited safety layer rather than unrestricted API access.
Requirements
A remote endpoint at mcp.sadasend.com over streamable HTTP; no local package or runtime needed. OAuth authentication is required, so a Sadasend account is needed. No environment variables or headers are declared.
Before you install
The server can send email, which is an outward-facing action that reaches real recipients. SpendGuard implies money-related limits, so review how spending is capped before use. The tool list is not published, so confirm exactly which 12 tools are exposed and what they can do before granting access.

Installation

In SourceWeft

  1. Open Sadasend 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.SadaSend%2Fsadasend/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": {
    "sadasend": {
      "type": "http",
      "url": "https://mcp.sadasend.com/"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 26, 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.