Skip to main content
Glama

Related Servers

Alternatives to md-to-word

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to convert PDF, Word, PowerPoint, Excel, HTML, EPUB, Outlook messages and web pages into Markdown for LLM and RAG workflows. Runs over stdio or HTTP and reproduces Microsoft markitdown's output byte for byte without a Python environment.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables authors and agents to compose, validate, and render long-form nonfiction Markdown using a vocabulary of delivery roles and rhetorical modifiers. It inspects documents for structural problems and outputs ready-to-publish Ghost, HTML, PDF, EPUB, DOCX, and RTF renderings.
      PolyForm Noncommercial 1.0.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to convert GitHub Flavored Markdown into formatted Word (.docx) files, including headings, lists, tables, links, code and images, with an optional Chinese official document (公文) font preset. Conversion runs locally, so no content is uploaded.
      115 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Converts DOCX/XLSX to Markdown with native OOXML chart-data extraction (reads numCache/strCache directly, no OCR or rasterization) and zero-loss composite-figure markers. Ships a CLI, an MCP server (stdio + Streamable HTTP), and an optional VLM fallback for figures with no native chart data.
      61 PyPI
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: validate_manuscript checks syntax, compile_markdown produces the document, extract_format_from_docx derives formats, and list_presets/inspect_preset form a clear list-vs-detail pair. The one real overlap is get_guide versus get_manual, both being 'read the documentation' tools differentiated only by short-vs-full scope, which risks misselection.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern (get_guide, list_presets, inspect_preset, validate_manuscript, compile_markdown, extract_format_from_docx). The verbs are used predictably: get_ for reading docs, list_/inspect_ for presets, validate_/compile_/extract_ for operations.

    Tool Count5/5

    Seven tools is well-scoped for a Markdown-to-Word pipeline: two documentation readers, one validator, two preset tools, one format extractor, and one compiler. Each tool maps to a distinct step in the workflow and none appears redundant.

    Completeness4/5

    The lifecycle is largely covered: learn the contract (get_guide/get_manual), inspect presets, derive a format from a reference docx, validate, then compile. The gap is format authoring — extract_format_from_docx produces a draft with 'to confirm' items, but there is no tool to validate or finalize a format file, and the custom cover/front-matter features described in §9 have no direct tool support, requiring manual file editing.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled