Docling-rs MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --http | No | Serve the MCP server over Streamable HTTP instead of stdio. | false |
| --root | No | Directory under which local file reads are restricted. | |
| --allow-url-fetch | No | Allow fetching documents from URLs. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Converts documents to Markdown or docling JSON for reading: PDF (layout, tables, OCR), DOCX, PPTX, XLSX, HTML, EPUB, e-mail, images, audio and more. Tools: convert_to_markdown for Markdown with default settings; convert for any other output format or for options (e.g. {"pages": "1-5"}); list_input_formats to check what this server accepts. Local files: paths under /app. URLs: enabled.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convertA | Convert a document to a chosen output format, with conversion
options, and return the result as text. |
| convert_to_markdownA | Read a document as Markdown, with default settings, and return the
Markdown text. Handles PDF (layout analysis, tables, OCR for scans),
Word, PowerPoint, Excel, HTML, EPUB, e-mail, images, audio and more.
Use this whenever Markdown is all you need. Use |
| list_input_formatsA | List the file extensions this server can convert, one per line, and
whether it accepts http(s) URLs. Takes no arguments and converts
nothing. Call it before |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
convert and convert_to_markdown overlap because convert can also produce Markdown, but the descriptions clearly position convert_to_markdown as the simple default and convert as the option-rich general path. list_input_formats has a clearly distinct discovery role.
Names are consistently snake_case and mostly verb_noun (convert_to_markdown, list_input_formats). The bare verb 'convert' is a minor deviation but still readable and predictable in context.
Three tools are well scoped for a focused document-conversion server: one generic converter, one Markdown convenience path, and one capability-discovery tool. Each earns its place without bloat.
The surface covers the core conversion workflow across many formats, including options, error behavior, and supported-format discovery. A minor gap is the lack of explicit batch conversion or output-to-file operations, though returning text is a workable contract.