ReadAnyDoc
Related Servers
Alternatives to ReadAnyDoc
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConvert PDF documents to Markdown and query them using AI with source attribution and confidence scoring, supporting multiple LLM providers.MIT
- AlicenseNot gradedqualityBmaintenanceEnables native multimodal reading of PDF documents through local or OpenAI-compatible vision-language models, converting pages into grounded Markdown with tables, equations, charts, and page-cited synthesis.MIT
- AlicenseAqualityCmaintenanceEnables OCR-enabled PDF to Markdown conversion in Claude Code, with per-page inspection and hybrid handling of text, scanned, mixed, and blank pages via a local vision-model endpoint.3MIT
- AlicenseNot gradedqualityCmaintenanceConverts PDFs, Office files, spreadsheets, emails, audio, and more to Markdown locally, enabling AI assistants to read and process them without cloud upload.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-driven PDF document processing including PDF to Markdown conversion, intelligent text and table extraction, image extraction, format conversion between PDF/Word/Markdown, batch processing, and fuzzy search - optimized for LLM context and RAG workflows.2MIT
- AlicenseAqualityBmaintenanceLocal MCP server that converts PDF, Word, PowerPoint, Excel and more to Markdown on your machine, enabling coding agents like Claude Code and Cursor to read office files in the repo.375 npmMIT
TDQS
Scored across 2 tools
parse_document converts a document to Markdown, while extract_fields pulls structured values into a JSON Schema, so their outputs and use cases are clearly different. There is mild overlap since extraction implicitly parses the same file, but the descriptions make the boundary (freeform text vs. schema-bound values) reasonably clear.
Both tools follow the same snake_case verb_noun convention (parse_document, extract_fields) with no deviations. The naming is predictable and immediately readable.
Two tools is on the thin side, but for a focused document-reading server they cover the two core workflows: raw conversion and structured extraction. Both tools earn their place, though a third (e.g. batch or format listing) could add value.
The surface covers the main lifecycle: read a document and extract structured data with citations, across many formats and page ranges. Minor gaps exist, such as no batch/multi-file processing, no remote URL input, and no chunking guidance for very large documents.