The reason to use this over a local Markdown renderer is destination-specific output: what pastes cleanly into Google Docs is not what pastes cleanly into Slack, and one tool knows the difference across 8 targets. The privacy section is unusually direct — content sent for conversion is processed and returned without being stored, while documents you create stay in your account until you delete them.
A Node server over the Unmarkdown API. It converts Markdown into styled HTML for a chosen destination and template, and manages a document library — create, list, read, update and publish to a public URL.
- Markdown converted for 8 destinations — `google-docs`, `word`, `slack`, `onenote`, `email`, `plain-text`, `generic` and `html` — through `convert_markdown`
- 62 visual templates with light and dark themes, applied by id: `swiss`, `mono`, `github` and `terminal` are free; `executive`, `consulting` and `startup` are Pro
- Documents created, listed with pagination, fetched with full content, and updated in title, content, template, metadata or folder — `create_document`, `list_documents`, `get_document`, `update_document`
- A document published to a shareable public URL under `unmarkdown.com/d/your-slug` — `publish_document`
- Your API quota for the current billing month — `get_usage`
An Unmarkdown account and an API key beginning with `um_`, in `UNMARKDOWN_API_KEY`. `UNMARKDOWN_API_URL` is optional and defaults to `https://api.unmarkdown.com`. Launch it through `npx` with `-y` and `@un-markdown/mcp-server`, install globally and use `unmarkdown-mcp`, or connect to the remote endpoint at `https://unmarkdown.com/api/mcp`. Free covers 1,000 API calls a month at 10 req/sec; Pro is $8/mo billed annually for 10,000 calls at 30 req/sec, with overage at $1.00 per 1,000 additional calls. Markdown you convert is sent to `api.unmarkdown.com`.
One command plus a key — npm install -g @un-markdown/mcp-server, then supply credentials