Email Server

live.alpic.stagingPublished by staging.alpic.liveOfficial publisherv0.0.56Updated Oct 24, 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 gives an assistant email capabilities through a remote endpoint.

What you can do
This server exposes email functionality to an AI assistant over a remote streamable HTTP endpoint. The registry description states only that it provides email capabilities and is hosted on the Alpic platform; no individual tools are listed in the manifest or README, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to work with email and prefer a hosted endpoint over running a local package. Because the specific tools are undocumented, verify the available operations before relying on it.
Requirements
A remote MCP endpoint at the provider's staging URL, reachable over the network. No packages, environment variables, headers, or authentication are declared in the manifest.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to use it; treat email access as sensitive. The server is hosted on a staging domain, which suggests it may be unstable or not production-ready. No tools are documented, so what it can read, send, or change is unknown.

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%2Fnode-email-mcp-59eeb419/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-59eeb419.staging.alpic.live/"
    }
  }
}

Tools

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

Version history

1
  1. v0.0.56LatestSep 16, 2026

Score

56% 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

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • 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