Docling
Document extractionIndependent review. IonBin has no partnership with Docling and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.
A document converter for preparing PDFs, scans and Office files for review and retrieval. Supports local processing and structured exports; check tables and source references before reuse. Documentation checked; not hands-on tested.
Reference entry: listed because workflows on IonBin use it. IonBin has no affiliate or paid relationship with Docling.
- Preparing a document library with reviewable structure
- Keeping structured output alongside readable Markdown
- Treating conversion as a factual or completeness check
Top use cases
- Convert PDFs and scans into Markdown and JSON source ↗
- Process a local directory through the CLI source ↗
- Preserve document structure and available provenance in DoclingDocument source ↗
In depth
Review the structured output
Keep DoclingDocument JSON beside Markdown. The representation supports provenance and available layout information, but do not assume every export or input format preserves identical page anchors. source ↗
Local deployment
Remote model services require an explicit option; offline use also needs model artifacts prepared locally. Check the selected pipeline and later exports before treating the workflow as local. source ↗
Agent access
The project documents an MCP server with Claude Desktop and LM Studio setup. A local or remote conversion service still needs deployment-specific permissions and testing. source ↗
How to use it with AI
How Docling connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Claude Desktop setup is documented. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Docling named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Docling publishes an API, but this pairing still needs network, authentication and execution-scope checks. Docling API ↗Claude (incl. Claude Code) docs ↗ | No documented route | Not documented Verify which side exports and which imports, supported formats and permissions. Docling's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Docling file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Docling has an official MCP server and OpenAI Codex supports MCP, but Docling's docs don't name this pairing. Auth setup may differ. Docling MCP docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Docling publishes an API, but this pairing still needs network, authentication and execution-scope checks. Docling API ↗OpenAI Codex docs ↗ | No documented route | Not documented Verify which side exports and which imports, supported formats and permissions. Docling's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Docling file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Docling has an official MCP server and Google Antigravity supports MCP, but Docling's docs don't name this pairing. Auth setup may differ. Docling MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Docling publishes an API, but this pairing still needs network, authentication and execution-scope checks. Docling API ↗Google Antigravity docs ↗ | No documented route | Not documented Verify which side exports and which imports, supported formats and permissions. Docling's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Docling file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Agent compatibility
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is not recorded for this tool. |
| File upload / import | Yes | Official docs ↗ |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Appears in these proposed stacks
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Workflows using this tool
- Ask questions of local documents
- Redact documents before AI review
- Turn a PDF folder into checked, source-linked Markdown
Explained in the wiki
Review
No long-form review yet. Verdict is based on research, not hands-on testing.