Send Email

io.github.hal9aiPublished by GitHub account hal9aiv0.0.2Updated Oct 24, 2026

Send emails from natural language prompts.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant send emails from natural-language prompts.

What you can do
Send emails based on natural-language instructions given to the assistant. The server is reached as a remote endpoint rather than a local package, so the assistant connects to it directly. No tool list, instructions or README were supplied, so the exact operations and their parameters are not documented here.
When to use it
Useful when you want an assistant to compose and dispatch email from a plain-language request without setting up a local mail integration.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP. The manifest declares no authentication, environment variables or headers, and no local runtime or package is needed.
Before you install
Sending email is an outward-facing action that cannot be recalled once delivered, so review recipients and content before letting the assistant send. The manifest declares no authentication, so consider who can reach the endpoint and what identity mail is sent under. No tool list or documentation was provided to confirm what data is transmitted or stored.

Installation

In SourceWeft

  1. Open Send Email in the dashboard and add it to a workspace.
  2. 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.hal9ai%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.

{
  "mcpServers": {
    "send-email": {
      "type": "http",
      "url": "https://next.hal9.ai/mcp/mcpbuild/send-email"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.0.2LatestSep 16, 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 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 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.