MCP server for reading and editing Word (.docx) documents with track changes, comments, footnotes, and structural validation
Provenance-first change tracking for AI document edits — native Word track-changes + a portable, hash-chained .changex journal. Works with any model (MCP + CLI). docx · xlsx · csv · pptx · md.
Side-by-side diff for prose, not code: compare Word, LibreOffice and Markdown versions, follow moved text, see new and removed comments, restore tracked changes. AI review of the edits, or of a single document: problems marked in the text, fixes returned as tracked changes and comments in Word or LibreOffice. Two files, two folders or git.
Compare two Word documents (.docx) into a native Track Changes redline — word-level diffs, image-faithful, self-verifying. Built with Kimi K3 Agent Swarm.
Apply native Microsoft Word Track Changes and comments to DOCX files with minimal OOXML edits
revisedoc — Edit .docx files with tracked changes, comments, and revision history. CLI, Python API, and MCP server for AI agents.
Track-changes verification for bilingual DOCX translation files
Extracts and analyzes Word document revision history (insertions, deletions, moves) to detect editing patterns like paste bursts, author contributions, and thrashing behavior from Track Changes metadata.
latexdiff for whole projects: drop in two Overleaf zips or arXiv IDs and get a track-changes PDF with changed figures compared side by side.
To associate your repository with the track-changes topic, visit your repo's landing page and select "manage topics."