Distill MCP Server

Convert PDF, DOCX, XLSX, PPTX, HTML, audio to token-efficient Markdown for any MCP client.

Local serverstdioPython

What is the Distill MCP server?

Distill MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Convert PDF, DOCX, XLSX, PPTX, HTML, audio to token-efficient Markdown for any MCP client.

What you get

An MCP server that connects any MCP-compatible client to Distill, converting local documents to clean, token-efficient Markdown before the LLM reads them. Typical token reduction is 40–80% compared to raw document text, letting the model fit more content into its context window and reason over it faster.

What the assistant can call

Once Distill is connected, these are the calls the assistant has available:

  • Rules — 1. Call convert_and_save with the absolute file path before doing anything else with the document. 2. Use ONLY the Markdown output from
  • Usage — Say "convert using distill" followed by the file path: > Convert using distill C:\Users\me\Documents\report.pdf to markdown

Configuration and credentials

You will need one environment variable: DISTILL_MCP_CONFIG. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

distill-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Distill's toolset — Rules, Usage — is a fair guide to whether it matches your workflow. It is maintained by lakshgk; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the distill mcp server does with a few real requests.

Available tools

ToolWhat it does
Rules1. Call convert_and_save with the absolute file path before doing anything else with the document. 2. Use ONLY the Markdown output from convert_and_save as the document content. Never read the original file with filesyst
UsageSay "convert using distill" followed by the file path: > Convert using distill C:\Users\me\Documents\report.pdf to markdown

How to install the Distill MCP server

**Lightweight mode — Windows:**

```json
{
  "mcpServers": {
    "distill-mcp": {
      "command": "npx",
      "args": ["-y", "distill-mcp-server"],
      "env": {
        "DISTILL_MCP_CONFIG": "{\"mode\":\"lightweight\",\"python_path\":\"py\"}"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DISTILL_MCP_CONFIGConfiguration value read at startup.Optional

Example prompts to try

  • Use Distill to Rules.
  • Use Distill to Usage.

Frequently asked questions

It connects Distill to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Rules, Usage) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Distill directly.