A
licenseA
qualityA
maintenanceA "Virtual DOM" for Microsoft Word enabling AI to safely read, redline, and sanitize DOCX contracts without breaking formatting.
11
170
MIT
docx-mcp
by sontanon
Related Servers
Alternatives to docx-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI agents to edit Word documents using track changes, allowing lawyers to review each modification via Word's revision interface.5-
BitsBound MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI-powered contract analysis with partner-level redlines and real OOXML Track Changes for Claude Desktop and Claude.ai.12284 npmMIT- AlicenseAqualityBmaintenanceEnables 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.1013AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceEnables comparison of baseline and counter-party contract clause revisions, flags high-risk shifts in indemnity, IP assignment, liability caps, and non-solicitation, and generates legal redline summaries with severity and escalation verdicts.7-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables comparing baseline and counter-party contract drafts to flag high-risk clause shifts and synthesize legal redline summaries.7-
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
ResponsivenessLimited data