io.github.tidybytetools/pdf-table-pull-lite
OfficialRelated Servers
Alternatives to io.github.tidybytetools/pdf-table-pull-lite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables inspecting local PDFs and extracting tables into CSV, XLSX, or JSON with options for pages, merging, OCR, engine selection, headers, merged cells, regions, and columns.MIT
- AlicenseNot gradedqualityCmaintenanceExtracts text and tables from PDFs for AI agents via MCP, enabling structured data retrieval from invoices, reports, and statements.75 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to extract clean structured JSON tables from any PDF with per-cell citations to the source page.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to extract text locally from PDF files through a STDIO tool, returning full-document text, page-level paragraphs, extraction methods, warnings, and basic table readability, with English/German OCR fallback for scanned pages.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to read and process PDF files with intelligent file search, text extraction, image processing, and optional OCR support for scanned documents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-powered extraction and analysis of PDF documents with 40+ specialized tools for text, tables, images, layout analysis, security assessment, and document intelligence. Supports both text-based and scanned PDFs with OCR capabilities.576 PyPI11MIT
TDQS
Scored across 1 tool
There is only a single tool, so there is no possibility of selecting the wrong one. Its purpose—extracting tables from a local text PDF—is stated clearly and unambiguously.
The lone tool follows a clear snake_case verb_noun pattern (extract_pdf_tables). With one tool there is no convention mixing, and the name is self-describing.
A single tool is defensible for a deliberately 'lite', single-purpose extractor, but the surface is thin: there is no companion operation to inspect a PDF before extracting. It sits at the borderline of minimal rather than well-scoped.
The core extraction workflow is covered, including page ranges, strategy choice, and CSV output, but there are notable gaps: no way to discover page count or check whether a PDF is text-based, and scanned/image pages are simply skipped with no fallback. Agents working with real-world PDFs will hit these dead ends.