Skip to main content
Glama
adelaidasofia

parse-mcp

by adelaidasofia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to parse-mcp

No user-submitted related servers found.

    Related Servers

    • doc-ingestor-mcp

      saleemh
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that uses Docling to convert PDFs, Office documents, images, audio, and more into clean Markdown for AI processing and RAG pipelines.
      6
      -

    • docling-mcp

      mk20mm
      A
      license
      A
      quality
      C
      maintenance
      MCP server wrapping Docling to give text-only LLMs document vision via tools for converting PDFs, images, and Office files to Markdown, extracting tables, OCR, and RAG chunking.
      4
      1
      MIT

    • Document Tools

      zsanjay
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that converts and processes document formats such as DOCX and PDF into Markdown, enabling AI assistants to work with document contents.
      -

    • Document Parser MCP

      kgand
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that uses the Docling toolkit to convert various document formats, including PDFs, Office files, images, and audio, into clean Markdown for AI processing. It supports multiple processing pipelines like VLM and ASR with intelligent auto-detection and job queue management.
      2
      MIT

    • mcp-docs

      gmantovani2005
      A
      license
      Not graded
      quality
      C
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation3/5

    parse, parse_url, parse_to_vault, and interpret all build on the same underlying parse operation, so an agent could easily select the wrong variant when the target or output destination is not explicitly clear. The descriptions help, but the boundaries between these tools remain somewhat fuzzy.

    Naming Consistency4/5

    Most tools follow a predictable snake_case verb_noun pattern such as list_backends, chunk_text, and detect_doc_type. parse_to_vault and single-word verbs like parse, interpret, and benchmark are minor deviations, but the overall naming style is coherent.

    Tool Count5/5

    Eight tools is well-scoped for a document parsing server with diagnostics, vault integration, and chunking support. Each tool maps to a distinct workflow need, and none feel redundant or like filler.

    Completeness4/5

    The toolset covers the full parse-chunk-interpret workflow, plus backend diagnostics and vault output. The main gap is the lack of a batch or multi-document parsing operation, but agents can work around that with repeated calls.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources