Skip to main content
Glama
sontanon

docx-mcp

by sontanon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to docx-mcp

No user-submitted related servers found.

    Related Servers

    • adeu

      dealfluence
      A
      license
      A
      quality
      A
      maintenance
      A "Virtual DOM" for Microsoft Word enabling AI to safely read, redline, and sanitize DOCX contracts without breaking formatting.
      11
      166
      MIT

    • KitchenSink4Word

      KitchenSink4AI
      A
      license
      A
      quality
      A
      maintenance
      Enables full-featured editing of Word .docx files through natural language, including merge-aware table operations, bulk cell edits, footnotes/endnotes, TOC management, tracked changes, and document comparison.
      29
      250 PyPI
      9
      AGPL 3.0

    • legal-intake-mcp

      omarnagy91
      A
      license
      A
      quality
      C
      maintenance
      Enables law firms and legal professionals to turn Arabic and English contract files into structured, citable context, with clause segmentation, date conversion across Hijri and Gregorian calendars, party extraction, and anchor-based verification, all without API keys or network calls.
      6
      MIT

    • Word AI

      flyfish-dev
      A
      license
      B
      quality
      D
      maintenance
      Structure-preserving Word DOCX editing MCP server with a .NET Open XML backend and Office.js live sessions. Enables safe, auditable, incremental editing of Microsoft Word documents for AI agents.
      63
      14 npm
      10
      AGPL 3.0
    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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: extract, apply changes, validate, audit, and diff. However, validate_document_tool and audit_document_tool both inspect document structure and could be confused, and apply_changes_from_file is a redundant variant of apply_changes. Overall, the descriptions help clarify boundaries.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with lowercase underscores (extract_fragments, apply_changes, diff_fragments). The '_tool' suffix on validate_document_tool and audit_document_tool is a minor inconsistency, and apply_changes_from_file is long but clear. The naming is generally predictable.

    Tool Count5/5

    With 6 tools, the server is well-scoped for the domain of .docx extraction, tracked changes, validation, and comparison. Each tool contributes to a focused workflow, and the count is within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core lifecycle: extraction, applying changes, validation, auditing, and diffing. Minor gaps exist, such as no direct tool for creating documents or accepting/rejecting changes, and the extraction tool skips some elements. However, the primary redlining workflow is well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources