Skip to main content
Glama
NiuTrans

MCP Document Parse

by NiuTrans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MCP Document Parse

No user-submitted related servers found.

    Related Servers

    • mineru-docparse-mcp

      zhengjie9510
      A
      license
      A
      quality
      D
      maintenance
      Converts Word, PDF, PPT, and Excel documents to Markdown using the MinerU DocParse API. Supports synchronous parsing and async background tasks for large files.
      2
      1
      MIT

    • DocReaderMCP Server

      prafulsapkota
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading and streaming of organization document formats (PDF, DOCX, Excel, CSV, TSV, TXT) as Markdown, with support for page ranges and sheet selection.
      -

    • MarkItDown MCP

      xkiranj
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts various file types (documents, images, audio, web content) to markdown format without requiring Docker, supporting PDF, Word, Excel, PowerPoint, images, audio files, web URLs, and more.
      204 npm
      14
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as parsing various document formats into Markdown, leaving no room for confusion or misselection.

    Naming Consistency5/5

    The single tool name 'parse_document_by_path' follows a clear verb_noun pattern, and since there are no other tools to compare against, it is inherently consistent. No naming conventions are mixed or violated.

    Tool Count2/5

    A single tool is too few for the server's purpose of document parsing, as it suggests a thin surface that may lack essential operations like handling different parsing modes, error recovery, or batch processing. This minimal count limits functionality and could lead to agent workarounds.

    Completeness2/5

    The tool set is severely incomplete for document parsing; it only offers parsing by file path without support for operations like parsing from URLs, handling different output formats, validating documents, or managing parsing errors. This creates significant gaps that will likely cause agent failures in real-world scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources