PDF Processor Server
Related Servers
Alternatives to PDF Processor Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceAn MCP server that provides a tool to extract text content from local PDF files, supporting both standard PDF reading and OCR capabilities with optional page selection.133-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for reading, writing, and manipulating PDF files, including text extraction, metadata retrieval, and merging or splitting documents. It also enables users to create PDFs from plain text and convert specific pages or entire documents into images.37 npmISC
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive PDF processing capabilities including text extraction, image extraction, table detection, annotation extraction, metadata retrieval, page rendering, and document structure analysis.-
- AlicenseAqualityAmaintenanceA comprehensive MCP server with 37 tools for PDF operations including reading, searching, creating, merging, splitting, watermarking, form filling, and more, built on open-source libraries.3744 npm2MIT
- AlicenseAqualityDmaintenanceAn MCP server providing comprehensive PDF processing capabilities with 18 tools for text extraction, OCR, image conversion, metadata management, and optimization.181MIT
- AlicenseAqualityDmaintenanceA PDF MCP server for extracting text, rendered pages, tables, links, annotations, outlines, metadata, and text statistics from PDF files.121MIT
TDQS
Scored across 15 tools
Most tools have clear, distinct purposes (extract_text vs extract_text_by_page vs extract_metadata), but get_pdf_info and extract_metadata overlap conceptually, and upload_file accepts base64 dicts, making upload_file_base64 redundant. The three upload tools introduce ambiguity about which to use.
The majority of tools follow a verb_noun snake_case pattern (e.g., extract_text, merge_pdfs, upload_file). However, server_info lacks a verb, and pdf_to_images/images_to_pdf are noun_to_noun, creating minor inconsistencies in an otherwise predictable naming scheme.
15 tools is at the upper boundary of the ideal 3-15 range, but the coverage of PDF processing operations (extract, merge, split, rotate, convert, upload) justifies the count. A few upload variants could be consolidated, but the overall scale is reasonable for a specialized server.
The tool set covers core PDF lifecycle operations well: creation from images, text extraction, metadata, merging, splitting, rotation, and conversion to images. The main gap is the absence of any delete/remove operation for temporary resources, which can leave dead ends in workflows.