Email Server

live.alpic.stagingPublished by staging.alpic.liveOfficial publisherv0.1.14Updated Nov 1, 2026

An MCP server that provides email capabilities, hosted on Alpic platform

The publisher's own server: My MCP server

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A hosted MCP server that lets an assistant send emails through the Resend API, plus a simple greeting tool.

What you can do
  • Send an email through the Resend API, with HTML and/or plain-text body content.
  • Return a basic greeting from a simple demo tool.
When to use it
Useful when an assistant should be able to dispatch email notifications or messages from a conversation without a local mail setup. The greeting tool is only a connectivity check.
Requirements
A remote MCP endpoint over streamable HTTP; no package, environment variables or headers are declared. Sending mail depends on the server's own Resend configuration, which is not described.
Before you install
The send_email tool sends real email to recipients, so confirm addresses and content before use. No authentication is declared for the endpoint, and the Resend API key handling is not documented; treat the service as third-party infrastructure that sees message content.

Installation

In SourceWeft

  1. Open Email Server 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/live.alpic.staging%2Femail-server/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": {
    "email": {
      "type": "http",
      "url": "https://node-email-mcp-ead34801.staging.alpic.live/"
    }
  }
}

Tools

2

greet

A simple greeting tool

Parametersnamerequired

send_email

Send emails via Resend API. Provide html_content and/or text_content.

Parameterstagssubjectrequiredreply_tocc_emailsto_emailsrequiredbcc_emailsattachmentshtml_contentscheduled_atsender_emailrequiredtext_content

Version history

1
  1. v0.1.14LatestSep 16, 2026

Score

72% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

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

Other Alpic integrations