“What happened to the limitation of liability across the rounds?”
Claude explains how the position changed from one draft to the next.
Sample contract workflow
See Claude move from four Word drafts to a reviewable counterproposal.
The demo uses synthetic documents and normal user prompts. No client data, hidden edits or pre-recorded product responses.
1 minute 44 seconds · Veqtor v0.1.2 · Sample documentsWatch
A real Claude session with a disposable negotiation.
Claude compares the rounds, checks important wording and prepares a separate Word document. The original drafts stay unchanged.
Recorded with Veqtor v0.1.2Claude explains and drafts · Veqtor reads, checks and writes · You review
The “one command” line in the narration refers to Claude Code. Claude Desktop currently needs a short configuration edit. One correction: Veqtor 0.1.2 checks the new Word document before saving it; it does not reopen the saved copy for a separate final check.
Read the video transcript
Claude can reason about a contract, but chat alone cannot reliably inspect several Word drafts or create precise tracked changes. An MCP server gives Claude specialized tools for that work. Claude still does the reasoning. The server performs the document work and returns results we can check against the source.
Veqtor is an open-source MCP server for Word contract negotiations. It reads redlines, verifies quotations, and creates new drafts with real tracked changes.
In this demo, I ask what happened to the liability cap across four rounds. Veqtor extracts the tracked revisions. Claude turns the evidence into a clear explanation of how the cap and its carve-outs changed.
Then I ask for the counterparty's exact latest wording. Instead of relying on the summary, Veqtor checks the quotation against the source file, character for character, and returns the verified text.
Finally, I turn the review into an action: restore our 150% cap and the willful misconduct carve-out in a new round-five draft. The original stays untouched.
Veqtor checks every edit before writing, then re-checks the saved file. In this run, no unintended changes. That is MCP in practice: Claude does the reasoning; Veqtor does document work you can verify. It's free, open source, and installs with one command. You're welcome to try it.
The prompts
Ask in the language of the negotiation.
You do not need to know how Veqtor works inside. Describe the result you want, and Claude chooses the right step.
“Check the wording you quoted against the counterparty’s change.”
Veqtor compares the quote with that specific tracked change.
“Prepare our counterproposal in Word with tracked changes.”
Veqtor tests the requested edits together and creates a separate file for review.
Reproduce it
Try the same workflow with fresh sample documents.
After connecting Veqtor, create a disposable four-round negotiation in your home folder:
TerminalVeqtor 0.1.2
uvx --from "veqtor-mcp==0.1.2" veqtor-demo-rounds ~/veqtor-demo-roundsOpen a new Claude session and ask:
Using the Veqtor tools, what happened to the limitation of liability across the rounds in ~/veqtor-demo-rounds?
The sample is safe to discard and recreate. Use it to learn the workflow before pointing Claude at any real matter.
Use sample documents first
Never include client text, private local paths or activity-history files in a public support request.
Start with sample documents