docx-editinglisted

# Editing .docx Files with Safe-DOCX Safe-DOCX is a local MCP server for surgically editing existing `.docx` files. It preserves formatting, generates tracked-changes redlines, and runs entirely on the local filesystem — no hosted endpoint, no data leaves the machine. ## Safety Model - **Local-only stdio runtime** — the MCP server runs as a child process, never binds a port. - **Path policy** — only files under `~/` (home directory) and system temp directories are accessible. Symlinks must resolve to allowed roots. - **Archive guardrails** — zip bomb detection and hostile payload rejection protect against malformed `.docx` inputs. ## When to Use This Skill Use Safe-DOCX when you need to: - Change clauses or paragraphs in an existing `.docx` - Insert or delete content with formatting preservation - Add comments or footnotes for reviewers - Produce a tracked-changes redline from edits - Compare two `.docx` files into a redline - Extract revisions to structured JSON - Apply layout formatting (spacing, row heights, cell padding) ## Not for From-Scratch Generation Safe-DOCX edits already-existing `.docx` files — it does not create documents from blank. For new document generation, use a template-filling workflow (e.g. OpenAgreements). Safe-DOCX can refine generated docs downstream. ## Quick Start ``` 1. read_file(file_path="~/doc.docx") → see paragraphs + _bk_* IDs 2. grep(file_path="~/doc.docx", patterns=["target phrase"]) → find paragraph IDs 3. replace_text(se