Productivity · Remote MCP server
emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.emailmd/emailmd- Version
- 0.11.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- dev.emailmd
- Namespace
- Namespace verified by the MCP Registry via the domain emailmd.dev · how
- Listed under
- Email MCP servers
- Repository
- github.com/anypost/emailmd
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.emailmd.dev/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- emailmd 0.11.1 · protocol 2025-06-18
- Tools discovered
- 3:
render,lint,read_docs - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | emailmd | 0.11.1 | stdio |
How to connect emailmd
emailmd is a remote MCP server: there is nothing to install. Its endpoint is https://www.emailmd.dev/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: emailmd version 0.11.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y emailmd@0.11.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"emailmd": {
"command": "npx",
"args": [
"-y",
"emailmd@0.11.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| EmailchaserRun cold email outbound from an AI agent: campaigns, leads, replies, sender accounts, autopilot. | Remote · HTTPLive check: ✓ handshake |
| Emailens MCPAnalyze, audit, fix and diff HTML, MJML, Maizzle and React Email across 21 email clients. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Emailfinder MCPFind verified professional emails by name, domain, LinkedIn, or role. | Local · stdio |
| EmailMCPAI agent email - 23 tools free to read inbox, 28 paid to send. $9.99/mo. Token auto-provisioned. | Remote · HTTPLive check: ✓ handshake |
| eMailPlane MailEmail for AI agents: send, receive, threads, templates, domains and mailboxes on your own server. | Remote · HTTP |
| emailverifier.devVerify emails and domains for routing, disposable providers, role accounts, and SMTP risk. | Remote · HTTPLive check: sign-in required |
| EmbossTurn any PDF form into a fillable one, fill it from data or documents, verify it, and fax it. | Remote · HTTPLive check: sign-in required |
| emergencescience MCPPost bounties, solve tasks, earn credits on Emergence Science - the agent economy. | Local · stdio |