Emailmd vs Mailtea

A side-by-side look at the Emailmd and Mailtea MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Emailmd logoEmailmdCommunication · Local subprocess (stdio)Write and preview emails from your assistant. Renders markdown into email-safe HTML that holds up in Outlook and Gmail, lints drafts for deliverability problems, and returns a live preview link. Hosted with no API key, or run it locally with npx emailmd mcp.64GoodAuth: no auth requiredMailtea logoMailteaCommunication · Local subprocess (stdio)Send email and newsletters with Mailtea over MCP, plus skills for email and website design.45FairAuth: not declared

Verdict: choose Emailmd for communication work as a local process; choose Mailtea for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Emailmd logoChoose Emailmd when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Emailmd

Mailtea logoChoose Mailtea when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
Explore Mailtea

Feature & specification comparison

Rows where the two servers differ are marked.

SpecEmailmd logoEmailmdMailtea logoMailtea
CategoryCommunicationCommunication
Quality signal64/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,3820
Directory activity 3 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Emailmd tools

No tool names declared yet. Check the project README from the listing page.

Mailtea tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Emailmd

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "anypost-emailmd": {
      "command": "npx",
      "args": [
        "-y",
        "emailmd"
      ]
    }
  }
}

Mailtea

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mailtea": {
      "command": "npx",
      "args": [
        "-y",
        "plugins"
      ]
    }
  }
}

Frequently asked questions

Emailmd is categorized under Communication and uses a local stdio subprocess. Mailtea belongs to Communication and uses a local stdio subprocess. Pick Emailmd for communication work and Mailtea for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Emailmd is listed as free. Auth: no auth required. Mailtea has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add anypost-emailmd and mailtea as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Emailmd has a quality signal of 64/100 (Good) with 3 views, 0 installs and 1,382 GitHub stars. Mailtea has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.