Open-source toolkit from the Docling project for parsing PDF, DOCX, PPTX, XLSX, HTML, images, and more into a unified DoclingDocument, with advanced PDF understanding, OCR, and exports to Markdown and JSON for gen AI and RAG workflows.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
## Editorial notes
Docling is useful when Claude-adjacent teams need to turn real-world documents into clean, structured text for gen AI and RAG. It parses many formats — including advanced PDF understanding — into a unified DoclingDocument, then exports to Markdown, HTML, DocTags, or lossless JSON that downstream models and pipelines can consume.
This is distinct from existing agent-framework and workflow entries: rather than orchestrating agents, Docling focuses on the document-ingestion step that feeds them. It offers a CLI and Python SDK, plug-and-play integrations with LangChain, LlamaIndex, Crew AI, and Haystack, and local execution for sensitive or air-gapped data.
## Source notes
- The official repository describes Docling as simplifying document processing by parsing diverse formats, including advanced PDF understanding, and integrating with the generative AI ecosystem.
- Supported inputs include PDF, DOCX, PPTX, XLSX, HTML, EPUB, images (PNG, TIFF, JPEG), audio, email formats, and more; advanced PDF understanding covers page layout, reading order, table structure, code, formulas, and image classification.
- Output uses a unified DoclingDocument representation and can export to Markdown, HTML, DocTags, and lossless JSON.
- Docling provides local execution for sensitive data and air-gapped environments, extensive OCR for scanned documents, support for Visual Language Models, and audio ASR.
- Docling also ships an MCP server and an API server (docling-serve), and a simple CLI, alongside the Python SDK installed with `pip install docling`.
- The GitHub repository is `docling-project/docling`, is MIT licensed, and targets Python 3.10+.
## Duplicate check
Checked current `content/tools/`, `content/mcp/`, agents, skills, hooks, rules, commands, guides, open pull requests, and repository-wide content for `Docling`, `docling`, `docling-project`, `docling.ai`, `github.com/docling-project/docling`, `DoclingDocument`, and `document parsing for gen AI`. An existing tools entry lists Docling only as one supported document loader among many, and no dedicated Docling tools entry, Docling source URL duplicate, or open duplicate PR was found.
## Disclosure
Editorial listing. No paid placement or affiliate link is used.Docling is useful when Claude-adjacent teams need to turn real-world documents into clean, structured text for gen AI and RAG. It parses many formats — including advanced PDF understanding — into a unified DoclingDocument, then exports to Markdown, HTML, DocTags, or lossless JSON that downstream models and pipelines can consume.
This is distinct from existing agent-framework and workflow entries: rather than orchestrating agents, Docling focuses on the document-ingestion step that feeds them. It offers a CLI and Python SDK, plug-and-play integrations with LangChain, LlamaIndex, Crew AI, and Haystack, and local execution for sensitive or air-gapped data.
pip install docling.docling-project/docling, is MIT licensed, and targets Python 3.10+.Checked current content/tools/, content/mcp/, agents, skills, hooks, rules, commands, guides, open pull requests, and repository-wide content for Docling, docling, docling-project, docling.ai, github.com/docling-project/docling, DoclingDocument, and document parsing for gen AI. An existing tools entry lists Docling only as one supported document loader among many, and no dedicated Docling tools entry, Docling source URL duplicate, or open duplicate PR was found.
Editorial listing. No paid placement or affiliate link is used.
Show that Docling is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/tools/docling)Docling side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Open-source toolkit from the Docling project for parsing PDF, DOCX, PPTX, XLSX, HTML, images, and more into a unified DoclingDocument, with advanced PDF understanding, OCR, and exports to Markdown and JSON for gen AI and RAG workflows. Open dossier | Python framework for autonomous AI agents, traditional agents, custom tools, MCP tools, prebuilt autonomous agents, workspace-restricted file and shell operations, E2B sandbox execution, OCR, document processing, and vector storage integrations. Open dossier | Open-source Python AgentOS and multi-agent framework, evolved from AutoGen, for building conversable agents, group chats, swarms, human-in-the-loop workflows, tool use, RAG, code execution, and provider-backed agent systems. Open dossier | Local-first AI application for private chat, document RAG, workspace agents, MCP-compatible tools, model routing, memories, scheduled tasks, multimodal workflows, multi-user Docker deployments, and self-hosted agent automation. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | davion-knight | — | — | — |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | tools | tools | tools | tools |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | docling-project | Upsonic | AG2 | Mintplex Labs |
| Added | 2026-07-09 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | CLI | CLI | CLI | CLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Docling parses documents you supply, including untrusted PDF, Office, HTML, and image files, so run it in an appropriate environment when processing files from unknown sources. Advanced understanding, OCR, and Visual Language Model or speech features download and run AI models; the first run fetches model weights over the network unless a cache is pre-provisioned. The optional Docling API server (docling-serve) exposes a network service, so secure and authenticate it before making it reachable beyond localhost. Local execution supports air-gapped and sensitive-data workflows, but exported content still flows into whatever downstream pipeline, model, or store you send it to. Pin the Docling version and review model sources when using it in automated pipelines. | ✓Upsonic autonomous agents can use file operations, shell operations, custom tools, MCP tools, document processing, OCR, vector stores, and external model providers; scope every capability before using private data. The README says file and shell operations are restricted to the configured workspace and dangerous commands are blocked. Verify that boundary locally before relying on it for sensitive repositories or production systems. MCP tools can connect agents to external data sources and services; review server provenance, tool names, read/write behavior, credentials, and approval flow before enabling them. OCR and document loaders can parse invoices, PDFs, Office files, HTML, Markdown, JSON, YAML, XML, and other documents depending on installed extras; handle extracted text as sensitive. Optional sandbox, vector database, storage, model, embedding, and telemetry dependencies can introduce additional network calls, costs, and retention behavior. | ✓AG2 agents can converse, call tools, execute code, use retrieval systems, run browser workflows, and coordinate group chats; require explicit permissions and approval gates for high-impact actions. The upstream install docs and examples commonly involve provider credentials; keep API keys, config files, notebooks, and `.env` files out of commits and support tickets. Code execution, Docker, Jupyter, browser-use, and RAG extras can touch local files, network services, notebooks, databases, and external websites; scope them tightly before granting agent access. Multi-agent conversations can continue through nested chats, swarms, group chats, and custom reply handlers; define termination, escalation, retry, and human takeover behavior. Track the release roadmap before upgrading because deprecations and the v1.0 transition can change which APIs should be used for new work. | ✓AnythingLLM can run agents, scheduled tasks, MCP-compatible tools, browser-like workspace actions, developer APIs, and external model calls; scope tools and credentials before enabling them for users. The upstream Docker guide includes examples that add the SYS_ADMIN capability to the container. Review whether that capability is acceptable for the host before copying production run commands. Multi-user Docker deployments need normal production controls: authentication, TLS, network isolation, secret management, persistent-volume ownership, backups, and upgrade planning. Agent tools, custom agents, model routing, memories, and scheduled tasks can change behavior over time; use least privilege, logging, review gates, and rollback plans for write-capable workflows. Localhost services such as Ollama, Chroma, LocalAI, or LM Studio may need Docker host routing adjustments; avoid exposing local provider ports wider than intended. |
| Privacy notes | ✓Parsed documents can contain personal, confidential, or proprietary data; the DoclingDocument and exported Markdown, HTML, or JSON reproduce that content. Local execution keeps parsing on your machine, but downstream steps such as LLM calls, RAG stores, and logs that receive the exported content follow their own data-handling policies. First-run model downloads contact the model host (for example Hugging Face), so air-gapped setups should pre-fetch models to avoid outbound requests. Apply normal retention and access-control policies to exported documents, intermediate artifacts, and any logs produced by a parsing pipeline. | ✓Prompts, task descriptions, workspace files, shell output, custom tool inputs, MCP payloads, OCR text, document chunks, embeddings, vector records, model responses, traces, and logs may contain sensitive data. Configured model providers, MCP servers, OCR services, E2B sandboxes, vector databases, storage backends, and observability or telemetry integrations may receive task data depending on selected extras. The package dependency list includes Sentry SDK with OpenTelemetry support; review runtime telemetry configuration before production use. Keep provider keys, sandbox tokens, vector database credentials, storage URLs, workspace paths, extracted document text, and generated agent outputs out of public prompts, logs, issues, and examples. | ✓Prompts, messages, tool arguments, tool outputs, code snippets, notebook state, retrieved documents, vector-store contents, provider responses, traces, and execution logs may contain sensitive user or workspace data. Do not expose secrets, API keys, private file paths, customer records, internal documents, database rows, or raw exceptions through agent messages, logs, notebooks, screenshots, or public examples. Provider extras and retrieval integrations can route data through OpenAI, Anthropic, Google, AWS, local model servers, databases, vector stores, browser automation, or other third-party services. If AG2 is used for code execution or browser automation, define which files, domains, credentials, downloads, screenshots, and logs can be read or retained. | ✓Uploaded documents, parsed chunks, embeddings, workspace memories, prompts, chat history, agent state, scheduled task inputs, MCP payloads, provider responses, logs, and API calls may contain sensitive data. The README documents anonymous telemetry and an opt-out through DISABLE_TELEMETRY=true or the in-app privacy setting; review this before using regulated or confidential data. Even with telemetry disabled, outbound calls may still go to configured LLMs, embedding models, vector databases, external tools, cdn.anythingllm.com, GitHub, or GitHubusercontent depending on the deployment. Keep provider keys, JWT secrets, workspace invite links, storage paths, private documents, and generated citations out of public prompts, screenshots, issues, and examples. |
| Prerequisites |
|
|
|
|
| Install | — | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Build Python autonomous agents with custom tools, MCP tools, prebuilt agents, workspace restrictions, sandbox execution, OCR, and document workflows.
Build Python multi-agent systems with AG2, the open-source AgentOS evolved from AutoGen, including conversable agents, group chats, swarms, tools, human review, RAG, and code execution.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.