Skip to main content
Glama
README.md
# MarkItDown MCP

Convert plain text, `.txt` notes, JSON, CSV, and HTML into **Wiki-ready Markdown**.

Preview CSS + Copy toolbar JS ship **inside this package**:

```text
styles/rts-markdown-common.css
styles/rts-markdown-copy.js
```

No dependency on Organized-Reference for styles.

## Install

```bash
npm i -g @mhdd_24/markitdown-mcp
# or npx in Cursor mcp.json
```

## Cursor `mcp.json`

```json
"markitdown": {
  "command": "npx",
  "args": ["-y", "@mhdd_24/markitdown-mcp"],
  "env": {
    "MARKITDOWN_WORKDIR": "D:/Sublime - Related RTS/Organized-Reference",
    "MARKITDOWN_OUTDIR": "D:/Sublime - Related RTS/Organized-Reference",
    "SUBLIME_EXE": "C:/Program Files/Sublime Text/subl.exe"
  }
}
```

## Tools

| Tool | Purpose |
|:-----|:--------|
| `md_status` | Workdir / outdir / package styles / Sublime |
| `md_styles` | Paths to package `styles/` CSS + JS |
| `md_install_styles` | Wire Sublime MarkdownPreview to package styles |
| `md_convert` | Content or file → formatted `.md` |
| `md_convert_batch` | Convert folder + index |
| `md_format` | Normalize existing `.md` spacing |
| `md_preview` | Open `.md` in Sublime |

## First-time Sublime setup

In chat: **md_install_styles**  
Then open any `.md` → **Ctrl+Shift+M** → Copy Markdown / Copy Formatted.

## License

ISC

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Each tool maps to a distinct operation: status, styles, install styles, convert, batch convert, format, and preview. The only potential confusion is between md_status and md_styles, since both report on style paths and package state, but their purposes are still reasonably separable.

Naming Consistency4/5

All tools consistently use the md_ prefix and snake_case, with most names following a verb-first pattern like md_convert, md_format, and md_preview. The exceptions are the two noun-style informational commands md_status and md_styles, but they remain predictable and easy to distinguish.

Tool Count5/5

Seven tools is well-scoped for this server's purpose: conversion, batch conversion, formatting, preview, and style setup are all represented without redundant filler. Each tool earns its place in the workflow.

Completeness5/5

The tool set covers the full Markdown workflow: converting files, batch conversion, normalizing existing markdown, previewing in Sublime, and managing the styles needed for proper rendering. There are no obvious dead ends or missing core operations for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues