pdf-mcp
Related Servers
Alternatives to pdf-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA local MCP server that extracts text-layer content from PDF files, enabling AI agents to inspect, extract text, outlines, and page content.-
- AlicenseNot gradedqualityBmaintenanceMCP server that reads PDFs and exposes them as structured Markdown, metadata, outlines, images, and tables to LLM consumers via tools like pdf_read_markdown and pdf_info.Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to read, search, and analyze PDF files from local paths or URLs. It provides tools for extracting specific page ranges, searching for terms, and retrieving document metadata.420 npm1MIT
- AlicenseAqualityFmaintenanceAn MCP server that exports PDF documents to markdown format optimized for LLM processing.11BSD 3-Clause
- AlicenseNot gradedqualityCmaintenanceA local MCP server that drives PDFium and pypdf to perform comprehensive PDF operations including inspection, assembly, page editing, watermarking, rendering, extraction, form filling, encryption, compression, attachments, bookmarks, and metadata management.MIT
- AlicenseAqualityDmaintenanceFast, local PDF parsing as an MCP server with text extraction, bounding boxes, OCR, and visual citations. No cloud or API key required.5MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: get_page_image renders visual content, get_page_text extracts textual content, get_pdf_info provides metadata, get_table_of_contents retrieves structural outline, and search_text performs text search. The descriptions reinforce these distinct functions, making tool selection unambiguous.
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes (get_page_image, get_page_text, get_pdf_info, get_table_of_contents, search_text). The naming convention is perfectly uniform across all five tools, using snake_case throughout without any deviations.
Five tools is well-scoped for a PDF processing server, covering core operations without bloat. Each tool serves a specific, essential function (rendering, text extraction, metadata, navigation, and search), making the count appropriate and efficient for the domain.
The toolset covers most fundamental PDF operations well, including reading, extracting, navigating, and searching. A minor gap exists in write/modify operations (e.g., merging, splitting, or annotating PDFs), but the provided tools are sufficient for common agent workflows involving PDF analysis and content retrieval.