mcp-pandoc is a document conversion server implementing the Model Context Protocol (MCP) that leverages Pandoc to transform content between various document formats while maintaining formatting and structure. It allows AI assistants like Claude to handle document conversions directly within conversations.
Before using mcp-pandoc, ensure you have these essential components installed:
# 1. Install Pandoc (core conversion engine)
# macOS
brew install pandoc
# Ubuntu/Debian
sudo apt-get install pandoc
# Windows
# Download installer from: https://pandoc.org/installing.html
# 2. Install UV package (includes uvx command)
# macOS
brew install uv
# Windows/Linux
pip install uv
# 3. Install TeX Live (required only for PDF conversion)
# Ubuntu/Debian
sudo apt-get install texlive-xetex
# macOS
brew install texlive
# Windows
# Install MiKTeX or TeX Live from https://miktex.org/ or https://tug.org/texlive/
Configure Claude Desktop to use mcp-pandoc:
~/Library/Application\ Support/Claude/claude_desktop_config.json
%APPDATA%/Claude/claude_desktop_config.json
Add this configuration:
{
"mcpServers": {
"mcp-pandoc": {
"command": "uvx",
"args": ["mcp-pandoc"]
}
}
}
mcp-pandoc supports bidirectional conversion between these formats:
Category | Formats | Requirements |
---|---|---|
Basic | MD, HTML, TXT, IPYNB, ODT | None |
Advanced | DOCX, PDF, RST, LaTeX, EPUB | Must specify output_file path |
Note: PDF is an output-only format. Converting from PDF to other formats is not supported.
To convert content directly in the conversation:
Convert this text to HTML:
# Sample Heading
This is a test paragraph with **bold** and *italic* formatting.
- List item 1
- List item 2
For converting between file formats:
Convert /path/to/input.md to PDF and save as /path/to/output.pdf
For DOCX output with custom styling:
Convert input.md to DOCX using template.docx as reference and save as output.docx
To create a reference document:
pandoc -o custom-reference.docx --print-default-data-file reference.docx
Create YAML configuration files for consistent formatting:
# academic-paper.yaml
from: markdown
to: pdf
number-sections: true
toc: true
metadata:
title: "Academic Paper"
author: "Research Team"
Use with:
Convert paper.md to PDF using defaults academic-paper.yaml and save as paper.pdf
PDF Conversion Fails
File Conversion Fails
Format Conversion Fails
Reference Document Issues
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "mcp-pandoc" '{"command":"uvx","args":["mcp-pandoc"]}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"mcp-pandoc": {
"command": "uvx",
"args": [
"mcp-pandoc"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"mcp-pandoc": {
"command": "uvx",
"args": [
"mcp-pandoc"
]
}
}
}
3. Restart Claude Desktop for the changes to take effect