MailMask

studio.mailmaskPublished by mailmask.studioOfficial publisherv0.1.0Updated Oct 24, 2026

Email for agents: domains, aliases, IMAP mailboxes, DNS, sending and webhooks via one API key.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureCommunication & Collaboration

Overview

AI-generated overview

MailMask gives an assistant email capabilities for agents — domains, aliases, IMAP mailboxes, DNS, sending and webhooks — through one API key.

What you can do
  • Manage email domains and DNS records for agent-owned addresses.
  • Create and manage aliases and IMAP mailboxes.
  • Send email and receive events through webhooks.
  • All of this is exposed through a single API key rather than separate integrations.
When to use it
Useful when an assistant needs its own email identity: provisioning a domain or alias, reading a mailbox over IMAP, sending mail, or reacting to incoming mail through webhooks.
Requirements
A remote MCP endpoint at the provider's site, reached over streamable HTTP. OAuth authentication is required; the service is described as working with one API key. No environment variables or headers are declared.
Before you install
The server can send email and change DNS records, which are outward-facing actions; confirm before letting an assistant do either. It requires OAuth credentials and an API key, so treat them as secrets. Mail content and domain configuration are handled by a third-party service.

Installation

In SourceWeft

  1. Open MailMask 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/studio.mailmask%2Fmailmask/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": {
    "mailmask": {
      "type": "http",
      "url": "https://www.mailmask.studio/mcp"
    }
  }
}

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

1
  1. v0.1.0LatestSep 19, 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.