Letterkeel: Send Email via SMTP, Resend, SendGrid & Mailgun

io.github.shawmena-dotcomPublished by GitHub account shawmena-dotcomv1.0.1Updated Oct 24, 2026

Letterkeel: send email from your own domain via SMTP, Resend, SendGrid, Mailgun, Postmark

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant send email from your own domain through SMTP, Resend, SendGrid, Mailgun or Postmark.

What you can do
Send email from your own domain through a chosen provider: SMTP, Resend, SendGrid, Mailgun or Postmark. The manifest lists no individual tools, so the exact operations are not documented here. Runs are executed on Apify and billed per accepted email recipient.
When to use it
Use it when an assistant should send transactional or outbound email from your own domain and you already use Apify and one of the supported email providers.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. OAuth authentication is required, with an Apify API token sent in the Authorization header as a Bearer token. An account with the chosen email provider (SMTP, Resend, SendGrid, Mailgun or Postmark) is also implied.
Before you install
Sending email is an outward-facing action that cannot be undone once delivered. Runs are billed per email recipient accepted to your Apify account, so usage costs money. The Authorization header carries your Apify API token, which must be kept secret. Email content and recipient data are processed by Apify and the chosen email provider.

Installation

In SourceWeft

  1. Open Letterkeel: Send Email via SMTP, Resend, SendGrid & Mailgun 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.shawmena-dotcom%2Fsend-email/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": {
    "letterkeel-send-email-via-smtp-resend-se": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cybermax/send-email"
    }
  }
}

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

2
  1. v1.0.1LatestSep 26, 2026
  2. v1.0.0Sep 25, 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.