MCP Pandoc logo

MCP Pandoc

by vivekvells

Converts document content and files between Pandoc-supported formats through MCP, including Markdown, HTML, DOCX, PDF, and more.

Install MCP Pandoc

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "vivekvells-mcp-pandoc": {
      "command": "uvx",
      "args": [
        "mcp-pandoc"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 1 tools correctly (29d ago).

Overview

vivekvells/mcp-pandoc MCP server exposes Pandoc-based document conversion through MCP. It accepts content or an input file, lets the caller specify source and target formats, and can return basic-format results inline or write advanced-format outputs to a file. Supported conversions include Markdown, HTML, DOCX, ODT, RST, LaTeX, EPUB, IPYNB, TXT, PDF output, and PPTX output. Reach for it when an MCP client needs repeatable document transformations, reference-document styling, Pandoc defaults files, or conversion filters.

Use cases

  • Convert Markdown into DOCX files
  • Generate PDFs from Markdown with Pandoc options
  • Transform HTML or DOCX into other supported formats
  • Apply reference-document styling to office documents
  • Reuse YAML defaults and filters across conversions

Key features

  • Convert content or files through Pandoc
  • Support Markdown, HTML, DOCX, ODT, RST, LaTeX, EPUB, IPYNB, and TXT
  • Produce PDF and PPTX output
  • Apply reference documents for DOCX, ODT, and PPTX styling
  • Use YAML defaults files and Pandoc filters

Tools1

What MCP Pandoc lets your agent do. Expand a tool for its parameters.

Verified live~1.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/19 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · mcp-pandoc (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars584Stargazers on the source repository.
Last commit2mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Pandoc works

What vivekvells/mcp-pandoc MCP server does

vivekvells/mcp-pandoc MCP server connects an MCP client to Pandoc for document format conversion. The conversion tool can work from raw text supplied in contents or from a complete input-file path. Callers specify the source and destination formats, with Markdown used as the default input and output format when those values are not provided.

The server supports reading and writing Markdown, HTML, DOCX, ODT, RST, LaTeX, EPUB, IPYNB, and TXT. PDF and PPTX are write-only in the documented interface: the server can produce them but does not accept them as input. Basic-format results can be returned inline, while advanced output formats require an output path according to the tool documentation.

How it works

The MCP tool named convert-contents receives conversion parameters and passes the work to Pandoc through the project’s Python package foundation. Its inputs include contents, input_file, input_format, output_format, output_file, reference_doc, defaults_file, and filters.

Use reference_doc when generating DOCX, ODT, or PPTX and applying styles from a template. The reference document must use the same format as the requested output. A YAML defaults file can hold reusable Pandoc options such as metadata, a table of contents, or section numbering. Filter paths can also be supplied as an array for custom processing.

Setup and configuration

The published package can be launched with uvx mcp-pandoc in an MCP client configuration. The server itself does not document credential or API-key configuration. Pandoc must be installed separately because it is the conversion engine. PDF output additionally requires a TeX Live installation.

A typical MCP configuration uses the uvx command with mcp-pandoc as its argument. Input and output paths should be complete paths with filenames and extensions when working with advanced formats. If an advanced conversion has no output path, the documentation notes that a temporary system path may be used.

Tools and capabilities

The documented conversion inputs provide these capabilities:

  • Convert inline content or a file between supported formats.
  • Select source and target formats explicitly.
  • Write DOCX, ODT, PDF, PPTX, RST, LaTeX, and EPUB results to files.
  • Apply a matching reference document for DOCX, ODT, and PPTX styling.
  • Reuse conversion settings from a Pandoc YAML defaults file.
  • Run specified Pandoc filters during conversion.

Limitations and notes

PDF cannot be read by Pandoc and is available only as an output format here. PPTX input is also not offered by this project, while PPTX output is supported. PDF generation depends on TeX Live, and the README identifies PDF support as still under development. The project is described as early development, so available behavior and tools may change.

Its format support therefore also depends on the installed Pandoc environment and the requirements of the requested output format.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Pandoc

Configure an MCP client to run `uvx mcp-pandoc`. Install Pandoc separately; PDF output also requires TeX Live.

The supplied configuration uses the standard `mcpServers` structure and the README demonstrates document conversion with Claude, but it does not explicitly name Claude Desktop.

Yes. PDF is supported as an output format, but PDF generation requires TeX Live and PDF support is described as under development.

No. The documented interface treats PDF and PPTX as write-only output formats; they are not offered as inputs.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Pandoc AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vivekvells-mcp-pandoc?style=directory)](https://allmcps.com/mcp/vivekvells-mcp-pandoc)
HTML Embed
<a href="https://allmcps.com/mcp/vivekvells-mcp-pandoc"><img src="https://allmcps.com/api/badge/vivekvells-mcp-pandoc?style=directory" alt="MCP Pandoc on AllMCPs" /></a>