Docling MCP Server

TypeScript SDK for Docling - Bridge between Python Docling ecosystem and JavaScript/TypeScript. Supports both CLI and API modes with dual publishing.

Local serverstdioPython

What is the Docling MCP server?

If you already use Docling, the docling mcp server is the piece that lets your assistant work with it directly. TypeScript SDK for Docling - Bridge between Python Docling ecosystem and JavaScript/TypeScript. Supports both CLI and API modes with dual publishing.

What the server does

Docling SDK provides document conversion, OCR, and chunking capabilities in TypeScript. It supports three client modes: an API client for Docling Serve, a CLI client wrapping the Python Docling tool, and a Web OCR client running entirely in the browser via WebGPU/WASM. The SDK works across Node.js, Bun, Deno, browsers, and Cloudflare Workers.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Guides — The Guides tool exposed by this server
  • Reference — The Reference tool exposed by this server

Installation

Installation goes through your MCP client rather than a global install: point it at docling-sdk on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Credentials and setup notes

| Requirement | Version | |-------------|---------| | Node.js | >= 18.0.0 | | TypeScript (optional) | >= 4.9.0 | | Docling Serve (API mode) | Latest | | Python Docling (CLI mode) | Latest | | WebGPU/WASM (Web mode) | Chrome 113+ or WASM fallback |

Where it fits

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. Docling's toolset — Guides, Reference — is a fair guide to whether it matches your workflow. It is maintained by kauandotnet; 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.

Worth knowing first

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
GuidesThe Guides tool exposed by this server.
ReferenceThe Reference tool exposed by this server.

How to install the Docling MCP server

{
  "mcpServers": {
    "docling-1": {
      "command": "npx",
      "args": ["-y", "docling-sdk"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

| Requirement | Version | |-------------|---------| | Node.js | >= 18.0.0 | | TypeScript (optional) | >= 4.9.0 | | Docling Serve (API mode) | Latest | | Python Docling (CLI mode) | Latest | | WebGPU/WASM (Web mode) | Chrome 113+ or WASM fallback |

Example prompts to try

  • Use Docling to Guides.
  • Use Docling to Reference.

Frequently asked questions

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