Markdown To Whatsapp MCP server

Markdown to WhatsApp Converter

Convert standard Markdown into WhatsApp's formatting syntax — as a web page, an npm library, a command line tool or an MCP server for agents.

➡️ Go to the Live Tool

npm i markdown-to-whatsapp · npx markdown-to-whatsapp mcp

Purpose of this tool

WhatsApp uses a non-standard syntax for text formatting (e.g., bold, italic, ~strikethrough~). This is similar, but not identical, to standard Markdown.

This tool provides a simple way to convert text from Markdown sources (like text editors, Google Docs, etc.) into the format that WhatsApp expects, saving the need for manual correction.

The entire conversion process runs locally in your browser using JavaScript, and the parser ships with the page. No data is ever sent to a server — the only request that leaves the page is for the font.

Supported conversions

The script uses the marked library for proper AST-based parsing and handles:

Text styles

• Bold: text → text
• Italic: text or text → text
• Strikethrough: ~~text~~ → ~text~
• Inline code: code → code
• Bold+Italic: text → text (preserves both styles)

Headings

Headings are converted to bold text with level-specific emoji prefixes:

• # H1 → 📌 H1
• ## H2 → 🟠 H2
• ### H3 → 🟡 H3
• And so on...

The emoji prefix can be turned off in the UI (Headings · Emoji), leaving plain Title.

Lists

• Unordered lists: Uses * prefix with ◦ for nested levels
• Level 1: * Item
• Level 2: * ◦ Item
• Level 3: * ◦ ◦ Item
• Ordered lists: Preserves numbering, with ◦ marking nested levels
• 1. A / ◦ 1. A1 / ◦ ◦ 1. A1a / 2. B
• Task lists: - [x] → ☑, - [ ] → ☐, also inside ordered lists (1. ☑ done)
• Loose items: multiple paragraphs of one item are joined on a single line
• Block content in items: code blocks, blockquotes and nested lists are emitted on their own lines below the item

Bubble width

A WhatsApp bubble fits a fixed number of monospace characters on one line — about 26 on a 360 px phone, which is the default. Measure yours by sending yourself a code block and counting where it breaks, then set Width in the bar to that (the ? next to it says the same). The field accepts 10 to 80: no phone is outside that range.

The number is a property of the phone, not of any one table, so it governs everything monospace: tables degrade to stay under it, and the preview draws every code block exactly that wide, wrapping where the recipient's WhatsApp will wrap.

Tables

A table is rendered in one of two styles, chosen in the UI for the whole document or for one table at a time:

1. Auto (default): a drawn table inside a monospace block, as wide as it needs and never wider than the bubble — and the bulleted list when no box can be drawn at all.

+--------+-------------+
   | Name   | Description |
   +========+=============+
   | Value  | Details     |
   +--------+-------------+

1. List: always the bulleted list.

How the list is laid out

A list can group the cells in three ways. The converter guesses from the headers and the bold cells, and the guess can be overridden per table (Layout: Auto · Rows · Columns · Pairs):

Shortened. The full README is on GitHub.