Doc2x MCP Server
Related Servers
Alternatives to Doc2x MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables conversion between PDF/Office documents and structured JSON, supporting extraction and generation of document content.-
- AlicenseAqualityCmaintenanceEnables AI assistants to extract and structure content from documents (PDFs, images, Office files) using Upstage AI's document digitization and information extraction APIs.23MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with comprehensive document parsing capabilities including PDF text extraction, OCR, HTML-to-markdown conversion, table extraction, and summarization, optimized for agent workflows.34 npmMIT

docuprox-mcpofficial
AlicenseAqualityDmaintenanceEnables AI clients like Claude to process documents (invoices, passports, etc.) via the DocuProx API, with tools for submitting jobs, checking status, and retrieving results.55 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to parse and search documents including PDF, Word, Excel, PowerPoint, and images via OCR, with support for semantic search and batch processing.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables extraction of text, tables, and structured data from PDFs, images, and office documents using LandingAI's Agentic Document Extraction API. Supports both direct parsing and background job processing for large files with privacy-focused processing.-
TDQS
Scored across 13 tools
Most tools have distinct purposes, but there is some overlap in waiting/submission pairs that could cause confusion. For example, doc2x_convert_export_wait and doc2x_convert_export_result both relate to export jobs, and the distinction between waiting and checking status might not be immediately clear. However, the descriptions help clarify their roles, and the overall set is well-organized around parsing and conversion workflows.
Tool names follow a highly consistent pattern throughout, using a doc2x_ prefix with verb_noun combinations (e.g., convert_export_submit, parse_pdf_status). All names use snake_case uniformly, and the naming scheme clearly indicates the action and resource involved, making the set predictable and easy to navigate.
With 13 tools, the count is well-scoped for a PDF/document processing server. Each tool serves a specific function in parsing, converting, and managing tasks, with no obvious bloat or redundancy. The tools cover submission, waiting, status checking, and result handling, which is appropriate for the domain's asynchronous nature.
The tool set provides comprehensive coverage for PDF and image parsing, conversion, and result retrieval, including synchronous and asynchronous operations. Minor gaps exist, such as the lack of tools for deleting or managing tasks beyond status checks, but these are not critical for core workflows. The surface supports end-to-end processing from submission to download, with only slight omissions in task lifecycle management.