Mailyond

com.mailyondPublished by mailyond.comOfficial publisherv1.1.0Updated Oct 28, 2026

Read, reply to and send email across every domain you connect to Mailyond, via API key over HTTP.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Mailyond lets an assistant read, reply to and send email across every domain connected to a Mailyond account, using an API key over HTTP.

What you can do
  • Read email across the domains connected to a Mailyond account
  • Reply to existing messages
  • Send new email from connected domains
  • Work over HTTP with a Mailyond API key rather than a local process
When to use it
Useful when you want an assistant to handle email for one or more domains managed through Mailyond, such as triaging incoming mail, drafting replies or sending messages, without building your own mail integration.
Requirements
A remote Mailyond endpoint reached over streamable HTTP. A Mailyond account and an API key with the myond_ prefix, created in the Mailyond dashboard and sent as a bearer token in the Authorization header.
Before you install
The server can send and reply to email, so messages may go out to real recipients on your behalf. The API key is a secret sent in the Authorization header; keep it out of logs and shared configuration. Email content from connected domains is handled by a third-party service.

Installation

In SourceWeft

  1. Open Mailyond 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.mailyond%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": {
    "mailyond": {
      "type": "http",
      "url": "https://mailyond.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

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

3
  1. v1.1.0LatestOct 26, 2026
  2. v1.0.1Oct 22, 2026
  3. v1.0.0Sep 16, 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.