Skip to main content
Glama
doc-extract-mcp

doc-extract-mcp

Related Servers

Alternatives to doc-extract-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to inspect, read in token-budgeted chunks, search, and extract tables and images from PDFs, plus merge, split, reorder, and rotate pages. Works with pure-Python dependencies and confines all file access to explicitly allow-listed folders.
      9
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to deterministically extract structured entities from input payloads and validate or coerce them against JSON schemas, returning a standardized response dossier with execution telemetry. It runs as a zero-dependency MCP server that plugs into Claude Desktop, Cursor, and other MCP clients.
      8
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading entire PDF documents into validated structured JSON, including tables, key-values, and markdown, with read-only extraction tools and layout reconstruction.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables read-only analysis of local unstructured documents by scanning a folder, extracting text and structural metadata, and passing content with truncation and error-awareness to an LLM for summarization.
      9
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives coding agents on-device OCR that turns images, PDFs and scans into Markdown with tables, plain text or JSON. Also fills a JSON Schema from a document using a local language model, with all processing kept on the machine.
      424 npm
      1
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: listing, reading, metadata, chunking, validation, and saving. No overlap; even read_document and chunk_document are clearly differentiated (full content vs. splitting for context). The separation is clean and unambiguous.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_documents, read_document, chunk_document, validate_json, save_structured). The exception is document_info, which uses a noun_noun form instead of get_document_info, creating a minor deviation from the otherwise predictable scheme.

    Tool Count5/5

    Six tools is an appropriate, well-scoped count for a document extraction server. Each tool covers a necessary step in the extraction workflow without redundancy or bloat.

    Completeness5/5

    The tool set provides a complete lifecycle for document extraction: discovering files (list), retrieving content (read), obtaining metadata (info), handling long documents (chunk), validating structured output (validate), and persisting results (save). No obvious gaps; the scope is tightly defined and fully covered.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data