Which integrations are available for this server?

Converts more than 29 file formats—including PDFs, Office documents, images, and audio files—into clean, structured Markdown for improved AI context processing. Enables the conversion of XML web content and documents into structured Markdown.

How do I use MarkItDown MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MarkItDown MCP Server Convert ~/Documents/annual_report.pdf to markdown" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MarkItDown MCP Server

by trsdn

Overview Schema Related Servers Score Discussions

Python

Hybrid

📄 MarkItDown MCP Server

MCP PyPI Python License Contributions Welcome

A powerful Model Context Protocol (MCP) server that converts 29+ file formats to clean, structured Markdown using Microsoft's MarkItDown library.

IMPORTANT

This is not Microsoft's official markitdown-mcp package. This is an independent community project published on PyPI as trsdn-markitdown-mcp. It uses Microsoft's markitdown library as a dependency, but it is developed and maintained separately from markitdown-mcp by Microsoft.

PyPI distribution name: trsdn-markitdown-mcp
Python import name: markitdown_mcp
CLI command: markitdown-mcp (alias: trsdn-markitdown-mcp)

🔥 Perfect for Claude Desktop, MCP clients, and AI workflows!

✨ Features

🔌 MCP Protocol: Seamless integration with Claude Desktop and MCP clients
📁 29+ File Formats: PDFs, Office docs, images, audio, archives, and more
🔍 Image Metadata: Extract EXIF metadata from images (JPG, PNG, GIF, etc.)
🎵 Speech Recognition: Convert audio to text with speech transcription (MP3, WAV)*

*Requires markitdown[all] installation for full functionality

📦 Dependency Requirements by File Type

File Type	Required Dependencies	Install Command
PDF	`pypdf`, `pymupdf`, `pdfplumber`	`pipx inject trsdn-markitdown-mcp 'markitdown[all]'`
Excel (.xlsx, .xls)	`openpyxl`, `xlrd`, `pandas`	`pipx inject trsdn-markitdown-mcp openpyxl xlrd pandas`
PowerPoint (.pptx)	`python-pptx`	Included in base install
Images	`PIL`, `exiftool` (optional)	Included in base install
Audio	`pydub`, `speech_recognition`	`pipx inject trsdn-markitdown-mcp 'markitdown[all]'`
Basic formats	None	Base install only

Note: For the best experience, we recommend installing all dependencies using the Complete Install method below.

📊 Office Documents: Word, PowerPoint, Excel files
🌐 Web Content: HTML, XML, JSON, CSV
📚 E-books & Archives: EPUB, ZIP files
⚡ Fast & Reliable: Built on Microsoft's MarkItDown library

Related MCP server: MarkItDown MCP Server

🚀 Quick Start for Claude Desktop

Install the server with ALL features:

# One command to install everything
pipx install trsdn-markitdown-mcp && \
pipx inject trsdn-markitdown-mcp 'markitdown[all]' openpyxl xlrd pandas pymupdf pdfplumber

Add to your Claude Desktop config:

{
  "mcpServers": {
    "markitdown": {
      "command": "markitdown-mcp",
      "args": []
    }
  }
}

Restart Claude Desktop and start converting files!

Features

Convert multiple file formats to Markdown
Batch processing of entire directories
Preserves directory structure in output
Environment variable support via .env file

📋 Available MCP Tools

🔧 `convert_file`

Convert a single file to Markdown.

{
  "name": "convert_file",
  "arguments": {
    "file_path": "/path/to/document.pdf"
  }
}

📋 `list_supported_formats`

Get a complete list of supported file formats.

{
  "name": "list_supported_formats",
  "arguments": {}
}

📁 `convert_directory`

Convert all supported files in a directory.

{
  "name": "convert_directory", 
  "arguments": {
    "input_directory": "/path/to/files",
    "output_directory": "/path/to/markdown" 
  }
}

📄 Supported File Formats (29+)

Category	Extensions	Features
📊 Office	`.pdf`, `.docx`, `.pptx`, `.xlsx`, `.xls`	Full document structure
🖼️ Images	`.jpg`, `.png`, `.gif`, `.bmp`, `.tiff`, `.webp`	EXIF metadata extraction
🎵 Audio	`.mp3`, `.wav`	Speech-to-text transcription
🌐 Web	`.html`, `.htm`, `.xml`, `.json`, `.csv`	Clean formatting
📚 Books	`.epub`	Chapter extraction
📦 Archives	`.zip`	Auto-extract and process
📝 Text	`.txt`, `.md`, `.rst`	Direct conversion

Installation

Published on PyPI as trsdn-markitdown-mcp — not to be confused with Microsoft's markitdown-mcp.

Option 1: Install from PyPI (Recommended)

# Isolated install with pipx
pipx install trsdn-markitdown-mcp

# Or with pip
pip install trsdn-markitdown-mcp

# Or run without installing (uv)
uvx trsdn-markitdown-mcp

Option 2: Install from source (development)

git clone https://github.com/trsdn/markitdown-mcp.git
cd markitdown-mcp
pip install -e ".[all]"

Option 3: Direct usage from a checkout

cd markitdown-mcp
python -m venv venv && source venv/bin/activate
pip install -r requirements.txt

Quick Start

MCP Server Mode (Recommended)

After installation:

# Start the MCP server (for use with MCP clients)
markitdown-mcp

# Equivalent alternatives
trsdn-markitdown-mcp
python -m markitdown_mcp

🛠️ Installation Options

🚀 One-Command Install (Recommended)

Install with ALL dependencies in one command:

# Using pipx (recommended)
pipx install trsdn-markitdown-mcp && \
pipx inject trsdn-markitdown-mcp 'markitdown[all]' openpyxl xlrd pandas pymupdf pdfplumber pytesseract pydub speechrecognition

# Or download and run the install script
curl -sSL https://raw.githubusercontent.com/trsdn/markitdown-mcp/main/scripts/install-all-deps.sh | bash

Quick Install (Basic Features Only)

pip install trsdn-markitdown-mcp

Complete Install with All Dependencies (Step by Step)

To ensure all file formats are supported, use one of these methods:

Method 1: Using pipx (Recommended)

# Install the MCP server
pipx install trsdn-markitdown-mcp

# Install all required dependencies for full functionality
pipx inject trsdn-markitdown-mcp 'markitdown[all]'         # PDF, OCR, Speech
pipx inject trsdn-markitdown-mcp openpyxl xlrd pandas      # Excel support
pipx inject trsdn-markitdown-mcp pymupdf pdfplumber        # Advanced PDF

Method 2: Using pip with virtual environment

# Create and activate virtual environment
python -m venv markitdown-env
source markitdown-env/bin/activate  # On Windows: markitdown-env\Scripts\activate

# Install with all dependencies in one command
git clone https://github.com/trsdn/markitdown-mcp.git
cd markitdown-mcp
pip install -e ".[all]"  # This installs everything!

Method 3: For Claude Desktop with existing installation

If you already have the MCP server installed but some formats aren't working:

# Find your installation
which markitdown-mcp  # Shows path like /Users/you/.local/bin/markitdown-mcp

# Inject missing dependencies
pipx inject trsdn-markitdown-mcp 'markitdown[all]' openpyxl xlrd pandas pymupdf pdfplumber

Verify Installation

After installation, verify the server responds to MCP requests:

# Ask the server for its tool list over stdio (JSON-RPC)
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | markitdown-mcp

# For pipx installations, check injected packages
pipx list --include-injected

🔧 Claude Desktop Configuration

Add this to your Claude Desktop claude_desktop_config.json:

{
  "mcpServers": {
    "markitdown": {
      "command": "markitdown-mcp",
      "args": []
    }
  }
}

Prefer running it without a permanent install? Use uvx (the package name is trsdn-markitdown-mcp, the command is markitdown-mcp):

{
  "mcpServers": {
    "markitdown": {
      "command": "uvx",
      "args": ["trsdn-markitdown-mcp"]
    }
  }
}

Config file locations:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

💡 Usage Examples

Convert a PDF

Convert the file ~/Documents/report.pdf to markdown

Batch Process Directory

Convert all files in ~/Downloads/documents/ to markdown

Check Supported Formats

What file formats can you convert to markdown?

🔍 Troubleshooting

Missing Dependencies Errors

If you see errors like:

PdfConverter threw MissingDependencyException
XlsxConverter threw MissingDependencyException
PptxConverter threw BadZipFile

This means some optional dependencies are missing. Follow the Complete Install instructions above.

Unicode Errors with .md Files

Some Markdown files with special characters may fail with UnicodeDecodeError. This is a known limitation in the MarkItDown library.

Installation Issues

"externally-managed-environment" error: Use pipx instead of pip
Permission denied: Never use sudo with pip; use pipx or virtual environments
Command not found: Make sure ~/.local/bin is in your PATH

See KNOWN_ISSUES.md for more details.

Configuration

No special configuration required. The tool uses the MarkItDown library for document conversion.

Usage

Basic Usage

# Convert all supported files from input/ to output/
python mdconvert.py

Custom Directories

Specify custom input and output directories:

python mdconvert.py --input /path/to/docs --output /path/to/markdown

Single File Conversion

Convert a single file:

python mdconvert.py --file document.pdf

Command Line Options

--input, -i: Input directory (default: input)
--output, -o: Output directory (default: output)
--file, -f: Convert a single file instead of a directory

MCP Server Features

The MCP server provides three tools:

1. convert_file

Convert a single file to Markdown.

Input: File path or base64 encoded content with filename
Output: Converted Markdown content

2. list_supported_formats

List all supported file formats.

Output: Categorized list of supported file extensions

3. convert_directory

Convert all supported files in a directory.

Input: Input directory path, optional output directory
Output: Summary of conversion results

Directory Structure

markitdown-mcp/
├── mcp_server.py        # MCP protocol server
├── mdconvert.py         # CLI script
├── mcp_config.json      # MCP configuration
├── requirements.txt     # Python dependencies
├── README.md           # This file
├── input/              # Default input directory
├── output/             # Default output directory
└── venv/               # Virtual environment

🔍 How It Works

This MCP server leverages Microsoft's MarkItDown library to provide intelligent document conversion:

📄 PDFs: Extracts text, tables, and structure
🖼️ Images: Uses OCR to extract text content + EXIF metadata
🎵 Audio: Converts speech to text transcription (MP3, WAV)
📊 Office: Preserves formatting from Word, Excel, PowerPoint
🌐 HTML: Converts to clean, readable Markdown
📦 Archives: Automatically extracts and processes contents

🏷️ Tags

mcp model-context-protocol claude-desktop markdown document-conversion pdf ocr speech-to-text markitdown ai-tools

📋 Requirements

Python: 3.10+
MCP Client: Claude Desktop or compatible MCP client
Dependencies: Automatically installed via pip

🤝 Contributing

We welcome contributions! Here's how you can help:

🚀 Quick Start for Contributors

# Fork and clone the repository
git clone https://github.com/YOUR_USERNAME/markitdown-mcp.git
cd markitdown-mcp

# Set up development environment
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -e ".[dev]"

# Test your changes
markitdown-mcp  # Test the server works

📝 Ways to Contribute

🐛 Bug Reports: Found an issue? Report it
💡 Feature Requests: Have an idea? Suggest it
📄 New File Formats: Add support for more file types
📚 Documentation: Improve guides and examples
🧪 Testing: Add tests and improve reliability
🎨 Code Quality: Refactor and optimize

📋 Contribution Process

Read our Contributing Guide
Check existing issues
Fork the repository
Create a feature branch (feat/amazing-feature)
Make your changes with tests
Submit a pull request

Please read docs/development/CONTRIBUTING.md for detailed guidelines.

📚 Documentation

For Users

Examples - MCP client configuration examples
Known Issues - Common problems and solutions
Changelog - Version history and updates

For AI Agents

AGENTS.md - Comprehensive guide for AI agent integration
API Documentation - Technical specifications and tool details

For Developers

Contributing Guide - How to contribute
Testing Strategy - Testing approach and guidelines
Documentation - Complete documentation index

📄 License

MIT License - see LICENSE file for details.

Model Context Protocol
Claude Desktop
Microsoft MarkItDown# Test workflow fixes

Test fix verification

Available Tools

3 tools

convert_directoryB

Convert all supported files in a directory to Markdown

ParametersJSON Schema

Name	Required	Description	Default
`input_directory`	Yes	Path to the input directory
`output_directory`	No	Path to the output directory (optional)

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Minimal behavioral disclosure beyond basic conversion; no details on default output directory, overwrite behavior, error handling (e.g., unsupported files), or performance implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence effectively communicates the core function with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple tool but missing details like subdirectory handling, supported file list, and return value; output schema absent but not required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; description adds no extra meaning beyond the schema (e.g., no examples or constraints for parameters).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it converts all supported files in a directory to Markdown, distinguishing it from sibling convert_file (single file) and list_supported_formats (listing formats).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives (convert_file, list_supported_formats), nor any context about prerequisites or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

convert_fileB

Convert a file to Markdown using MarkItDown

ParametersJSON Schema

Name	Required	Description
`file_path`	No	Path to the file to convert
`file_content`	No	Base64 encoded file content (alternative to file_path)
`filename`	No	Original filename when using file_content

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description must disclose behavioral traits. It omits supported input formats, output handling (e.g., return vs save), and potential side effects. Only states conversion to Markdown via MarkItDown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no unnecessary words. Concisely communicates core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing critical details: supported file types, output format details, error handling. No link to sibling 'list_supported_formats'. Incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds no additional meaning beyond schema parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Convert', the resource 'a file', the target format 'Markdown', and the tool 'MarkItDown'. It distinguishes itself from siblings 'convert_directory' and 'list_supported_formats' by specifying file-level conversion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. Does not explain when to use file_path versus file_content+filename, nor any prerequisites or restrictions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_supported_formatsA

List all supported file formats for conversion

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description only states the basic read operation. It does not disclose any behavioral details beyond listing formats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the purpose with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool (no parameters, no output schema), the description is sufficiently complete to inform an agent about its purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and 100% schema coverage, the description adds no additional parameter information, which is adequate but not enhanced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'supported file formats for conversion', and effectively distinguishes this tool from the sibling conversion tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool should be used before conversion to see available formats, but lacks explicit guidance on when to use it versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.2.1Jan 23, 2026
- First observedconvert_directory
- First observedconvert_file
- First observedlist_supported_formats

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: converting a single file, converting a directory, and listing supported formats. No overlap in functionality.

Naming Consistency5/5

All tools follow the snake_case verb_noun pattern (convert_file, convert_directory, list_supported_formats), providing a predictable and consistent naming convention.

Tool Count5/5

Three tools is appropriate for this focused server; each tool serves a necessary function and there are no redundant or missing core capabilities.

Completeness4/5

The tool set covers the primary operations for file conversion (single, batch, and format listing), though missing advanced options like output customization or conversion status checking.

Maintenance

ActivityMaintained

ResponsivenessResponsive

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Mdkit A
online.mdkit
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Developer Tools RAG Systems Data Platforms
31
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
PDF to Markdown (pdf2md.dev)
dev.pdf2md
Hosted MCP server: convert PDFs to clean, LLM-ready Markdown with tables, formulas and OCR.
AI & Machine Learning Image & Video Processing
2
inktomd MCP Server A
io.github.hadirizvi093
Convert files, URLs, and documents to clean, AI-ready Markdown via MCP.
File Systems Web Scraping Documentation Access
91

Related MCP Servers

Unstructured Document
Documentation Access Developer Tools Search
MKhalusova
F
license
B
quality
D
maintenance
A Model Context Protocol server that enables LLMs to extract and use content from unstructured documents across a wide variety of file formats.
Updated a year ago (2025-03-20 17:15 UTC)
1
11
-
MarkItDown MCP Server
Documentation Access File Systems
canlgz
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that converts various file formats (PDF, PowerPoint, Word, Excel, Images, etc.) to Markdown to make them accessible to LLMs.
Updated 2 years ago (2025-01-30 19:50 UTC)
1
MIT
DOCX MCP Server
zeph-gh
F
license
A
quality
D
maintenance
A comprehensive Model Context Protocol server that processes Microsoft Word documents with full formatting support, enabling text extraction, HTML/Markdown conversion, structure analysis, and image extraction.
Updated a year ago (2025-07-11 05:33 UTC)
5
2
-
Markdownify MCP Server
Multimedia Processing Documentation Access Web Scraping
anis-marrouchi
A
license
A
quality
D
maintenance
A Model Context Protocol server that converts diverse file types, including PDFs, images, audio, and Office documents, into Markdown format. It also transforms web content like YouTube transcripts and Bing search results into readable text for model consumption.
Updated a year ago (2025-09-19 15:38 UTC)
13
347
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trsdn/markitdown-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

📄 MarkItDown MCP Server

✨ Features

📦 Dependency Requirements by File Type

🚀 Quick Start for Claude Desktop

Features

📋 Available MCP Tools

🔧 convert_file

📋 list_supported_formats

📁 convert_directory

📄 Supported File Formats (29+)

Installation

Option 1: Install from PyPI (Recommended)

Option 2: Install from source (development)

Option 3: Direct usage from a checkout

Quick Start

MCP Server Mode (Recommended)

🛠️ Installation Options

🚀 One-Command Install (Recommended)

Quick Install (Basic Features Only)

Complete Install with All Dependencies (Step by Step)

Method 1: Using pipx (Recommended)

Method 2: Using pip with virtual environment

Method 3: For Claude Desktop with existing installation

Verify Installation

🔧 Claude Desktop Configuration

💡 Usage Examples

Convert a PDF

Batch Process Directory

Check Supported Formats

🔍 Troubleshooting

Missing Dependencies Errors

Unicode Errors with .md Files

Installation Issues

Configuration

Usage

Basic Usage

Custom Directories

Single File Conversion

Command Line Options

MCP Server Features

1. convert_file

2. list_supported_formats

3. convert_directory

Directory Structure

🔍 How It Works

🏷️ Tags

📋 Requirements

🤝 Contributing

🚀 Quick Start for Contributors

📝 Ways to Contribute

📋 Contribution Process

📚 Documentation

For Users

For AI Agents

For Developers

📄 License

🔗 Related

Test fix verification

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

🔧 `convert_file`

📋 `list_supported_formats`

📁 `convert_directory`