Sendfeather

com.sendfeatherPublished by sendfeather.comOfficial publisherv1.0.0Updated Oct 29, 2026

Send transactional email and check delivery: bounces, suppressions, per-provider stats.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Sendfeather lets an assistant send transactional email and check delivery activity such as bounces, suppressions and per-provider stats.

What you can do
  • Send transactional email through Sendfeather.
  • Check delivery activity: bounces, suppressions and per-provider statistics.
  • Read access is scoped by the read:activity permission and sending by the send permission on the API key.
When to use it
Useful when an assistant should trigger transactional emails or review delivery health and bounce/suppression data without leaving the conversation.
Requirements
A remote MCP endpoint at sendfeather.com over streamable HTTP. A Sendfeather account and an API key from the dashboard, supplied as a bearer token in the Authorization header. The key needs the read:activity scope for reads and the send scope for sending.
Before you install
The API key is a secret sent in the Authorization header; keep it scoped and rotate it if exposed. Sending email is an outward action that reaches real recipients, and reading activity exposes delivery and suppression data. Grant the send scope only when sending is intended.

Installation

In SourceWeft

  1. Open Sendfeather in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/com.sendfeather%2Fmcp/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.

{
  "mcpServers": {
    "sendfeather": {
      "type": "http",
      "url": "https://sendfeather.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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 29, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.