Use an MCP to edit Word docs with tracked changes

An agent can revise .docx files by editing HTML first, then translating the result back into Word’s file format.

Done with Custom agent· Intermediate

What they did
A custom-built agent was wired to an MCP for Word editing. It worked on an HTML version of the document rather than raw OOXML, and a small 3–8B LoRA model converted each altered block into OOXML. A deterministic matcher found the right block, then the system created tracked edits by comparing versions and patching the .docx.
How it went
On the vendor’s 279-task benchmark, the approach came out 2.7–2.9x less expensive and 2.7–3.5x quicker than Anthropic’s DOCX skill, with a better pass rate. Hyperlink handling lagged, at 25% pass rate. Comments, image attachments, and latent styles are not supported yet.
Tips
This fits documents where layout needs to stay intact and changes should be reviewable. Be cautious about the benchmark, since it is the vendor’s own.

Try it yourself with Claude Cowork

Load [file path] in Word and carry out these edits: [describe the changes]. Preserve the existing formatting, and show the edits as tracked changes. Save a separate copy named [new filename], not the original. Before any step that would permanently change, remove, send, or submit the file, stop and ask for my approval. When you’re done, summarize each edit you made.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.