Skip to main content
Glama
Mavline

docx_mcp_server_ts

by Mavline

Related Servers

Alternatives to docx_mcp_server_ts

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      Enables comprehensive DOCX/OOXML document manipulation via MCP, covering text, tables, images, content controls, comments, tracked changes, and metadata.
      34
      27 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Provides MCP tools for working with Microsoft Word documents, enabling reading, editing with tracked changes, formatting, table manipulation, comments, and PDF conversion via direct OOXML manipulation.
      37
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to generate, edit, validate, and render Word documents programmatically via MCP, ensuring correct OOXML structure and style.
      3
      MIT
    • A
      license
      D
      quality
      D
      maintenance
      Enables reading, writing, editing, and converting Office documents (ODT, DOCX, ODS, XLSX, PDF, etc.) using MCP tools, with no external dependencies.
      11
      32 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      An MCP server for reading, editing, and validating Microsoft Word documents with specialized support for track changes, comments, and footnotes. It enables structural auditing, heading extraction, and precise OOXML-level document manipulation through natural language tools.
      100
      55
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables document conversion and processing through MCP, including Office/PDF/Markdown conversions, OCR, and PDF operations like split, rotate, encrypt, and extract.
      MIT

    TDQS

    C2.9/5.0

    Scored across 29 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose (e.g., get_text vs. find vs. replace_text), with no overlapping functionality. The split between list/get/set operations across different document parts (tables, headers, styles) avoids ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_parts, part_read, table_edit) and share the 'docx.' prefix. The naming is uniform, lowercase with underscores, making it predictable and easy to navigate.

    Tool Count4/5

    With 29 tools, the count is higher than the typical 3-15 range, but it is justified by the comprehensive scope of DOCX manipulation (text, tables, images, styles, metadata, comments, etc.). It feels extensive rather than bloated, though slightly over the ideal range.

    Completeness4/5

    The tool set covers a wide range of DOCX operations including open/save, text handling, tables, images, styles, numbering, headers/footers, comments, changes, and metadata. Minor gaps exist (e.g., no explicit delete for tables or images, no create-new-document operation), but agents can likely work around these using existing tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues