MCP Pandoc MCP Server

A Model Context Protocol server for document format conversion using [pandoc](https://pandoc.org/index.html). This server provides tools to transform

Local serverstdioPython

What is the MCP Pandoc MCP server?

MCP Pandoc becomes available to MCP clients through the mcp pandoc mcp server. A Model Context Protocol server for document format conversion using pandoc. This server provides tools to transform content between different document formats while preserving formatting and structure.

What MCP Pandoc does

A Model Context Protocol server for document format conversion using pandoc. This server provides tools to transform content between different document formats while preserving formatting and structure.

Tools it exposes

Once connected, the assistant can call these 10 tools directly:

  • Inputs — - contents (string): Source content to convert (required if input_file not provided)
  • markdown — html
  • pdf — docx
  • rst — latex
  • epub — txt
  • ipynb — odt
  • Note — For advanced formats (pdf, docx, rst, latex, epub), an output_file path is required
  • Examples — The Examples tool exposed by this server
  • Testing — To run the comprehensive test suite and validate all supported bidirectional conversions, use the following command:
  • Debugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP

Installing the mcp pandoc mcp server

The server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: UV_PUBLISH_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • PDF (.pdf) - requires TeX Live installation - DOCX (.docx) - supports custom styling via reference documents - All others - no additional requirements Note: For advanced formats: 1. Complete file paths with filename and extension are required 2. PDF conversion requires TeX Live installation (see Critical Requirements section -> For macOS: brew install texlive) 3. When no

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Pandoc sits in that group, and the shape of its toolset — Inputs, markdown, pdf among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • With 10 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use MCP Pandoc.
  • Maintained by vivekVells, written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp pandoc mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
Inputs- contents (string): Source content to convert (required if input_file not provided)
markdownhtml
pdfdocx
rstlatex
epubtxt
ipynbodt
NoteFor advanced formats (pdf, docx, rst, latex, epub), an output_file path is required
ExamplesThe Examples tool exposed by this server.
TestingTo run the comprehensive test suite and validate all supported bidirectional conversions, use the following command:
DebuggingSince MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).

How to install the MCP Pandoc MCP server

{
  "mcpServers": {
    "pandoc": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "UV_PUBLISH_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • PDF (.pdf) - requires TeX Live installation - DOCX (.docx) - supports custom styling via reference documents - All others - no additional requirements Note: For advanced formats: 1. Complete file paths with filename and extension are required 2. PDF conversion requires TeX Live installation (see Critical Requirements section -> For macOS: brew install texlive) 3. When no
VariableDescriptionRequired
UV_PUBLISH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Pandoc to Inputs.
  • Use MCP Pandoc to markdown.
  • Use MCP Pandoc to pdf.

Frequently asked questions

It connects MCP Pandoc to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (Inputs, markdown, pdf, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Pandoc directly.