MarkItDown MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBLIME_EXE | No | Path to the Sublime Text executable. | |
| MARKITDOWN_OUTDIR | No | The output directory for converted Markdown files. | |
| MARKITDOWN_WORKDIR | No | The working directory for MarkItDown conversions. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| md_statusB | Check MarkItDown MCP: workdir, outdir, package-local styles (CSS/JS Copy toolbar), and optional Sublime path. |
| md_stylesA | Report package-local style/JS paths (markitdown-mcp/styles/rts-markdown-common.css + rts-markdown-copy.js) and whether they exist. |
| md_install_stylesB | Wire Sublime Text MarkdownPreview to this package styles/ folder (CSS + Copy JS). Writes/updates Packages/User/MarkdownPreview.sublime-settings. |
| md_convertB | Convert plain text content or a file (.txt/.json/.csv/.html/.md and more) into properly formatted Wiki-ready Markdown. Writes a .md file under MARKITDOWN_OUTDIR (or outputPath). Output is pure Markdown so Sublime MarkdownPreview can use this package styles/ CSS + Copy Markdown / Copy Formatted buttons. |
| md_convert_batchA | Convert all matching files in a folder (default *.txt) to Markdown. Same formatting rules as md_convert. |
| md_formatA | Normalize an existing .md file (fence spacing, blank lines around tables/headings) without removing content. Keeps Wiki + Sublime preview consistency. |
| md_previewB | Open a Markdown file in Sublime Text. Preview with Ctrl+Shift+M uses this package styles/ CSS + Copy Markdown / Copy Formatted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.