Plainmail

dev.plainmailPublished by plainmail.devOfficial publisherv1.1.1Updated Nov 7, 2026

Email on your own domains: add a domain, write its DNS, create mailboxes, read and send mail.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureCommunication & Collaboration

Overview

AI-generated overview

Plainmail gives an assistant real mailboxes on your own domains: add a domain, write its DNS records, create mailboxes, then read, send and reply to mail.

What you can do
  • Add a domain and create mailboxes on it
  • Write MX, SPF, DKIM and DMARC records at a DNS host, or hand back records to copy elsewhere, and wait until they are live
  • Read mail in a mailbox
  • Send mail and reply to messages
  • Manage domains and mailboxes, subject to the permissions you grant
When to use it
Useful when you want an assistant to set up a new email address on a domain you own and then handle that inbox — reading, sending and replying — without switching to a separate mail client.
Requirements
A remote MCP endpoint reached over streamable HTTP; sign in with OAuth (no API key needed) or send a Plainmail API key in the Authorization header. A Plainmail account is required, billed at $5 a month for up to 50 domains. DNS access at Cloudflare, Vercel or Porkbun for automatic record writing, or the ability to add records manually elsewhere.
Before you install
The server can send and reply to mail and change DNS records on your domains, so grant only the permissions you need. It is a paid service. An API key sent in the Authorization header is a credential to keep private. Mail content and domain settings are handled by Plainmail as a third party.

Installation

In SourceWeft

  1. Open Plainmail 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/dev.plainmail%2Fmail/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": {
    "plainmail": {
      "type": "http",
      "url": "https://app.plainmail.dev/api/mcp/mcp"
    }
  }
}

README

Plainmail for Claude

Real mailboxes on your own domains, set up and handled from Claude. Ask "set up [email protected]" and Claude adds the domain to Plainmail, writes the MX, SPF, DKIM and DMARC records at your DNS host (Cloudflare, Vercel or Porkbun, or gives you the records to copy anywhere else), waits until they're live and creates the mailbox. After that it can read, send and reply to mail on that address. The mailbox is a normal IMAP account, so it also works in Apple Mail, the Gmail app, Outlook or Thunderbird.

What's inside

  • The Plainmail remote MCP server (https://app.plainmail.dev/api/mcp/mcp), signed in with OAuth. No API key to copy.
  • A set-up-email skill with the setup steps.

Install

/plugin marketplace add jdcodes1/plainmail-claude-plugin/plugin install plainmail@plainmail

Then run /mcp, pick plainmail and sign in. You choose which permissions to allow: read mail, send and organize mail, and manage domains and mailboxes.

You need a Plainmail account ($5 a month for up to 50 domains).

Links

Source: README.md at commit 1099e06

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

3
  1. v1.1.1LatestNov 7, 2026
  2. v1.1.0Nov 6, 2026
  3. v1.0.0Nov 5, 2026

Score

85% 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
  • License10 pts