How to Use Claude with Word Documents: The Complete Guide

Claude can work with Word documents in three different ways, and which one you choose determines what kind of output you get. You can paste text into Claude's chat window, upload a .docx file directly, or connect the Scaffold MCP connector to give Claude full Word editing capabilities — including the ability to produce a downloadable .docx with real tracked changes. The first two are fast to start but limited in output; the third requires a few minutes of setup and unlocks a professional-grade workflow.

This guide walks through all three in detail so you can decide which fits your use case.

Can You Just Paste Your Document Text Into Claude?

Yes, and for simple tasks it works fine. Copy the text from your Word document, paste it into Claude's chat, and ask your question. Claude can summarize, identify issues, propose revisions, or answer questions about the content.

The limits are predictable. Pasting loses all formatting — paragraph structure, heading levels, table layouts, and bold/italic styling do not survive the paste. Long documents may exceed the amount of text that fits cleanly in one message, depending on which Claude plan you are on. And like all text-input methods, the output is text: Claude will give you revised paragraphs in the chat window, and you have to find those sections in your Word document and update them by hand.

This method is useful for short documents where you need a quick read and some suggested language. It is not practical for multi-section contracts, policy documents with complex structure, or any workflow where you need an audit trail of changes.

What Happens When You Upload a .docx Directly to Claude?

Claude (claude.ai, Pro and up) supports direct file upload. You click the attachment icon, select your .docx file, and Claude reads the full document content. Claude can then answer questions about it, summarize sections, identify clauses, flag missing provisions, or propose new language.

This is a meaningful step up from pasting. Claude reads the document as structured text rather than requiring you to copy it manually. You can upload a 50-page contract and ask Claude to identify every indemnification clause, every limitation of liability, or every place where a governing law provision appears — and Claude will find them.

What Claude still cannot do natively is produce a new .docx file. If Claude tells you "clause 12 should be revised to add a mutual obligation," the output is text in the chat window. You open your Word document, find clause 12, and type the change yourself. There is no tracked-change file, no download link, and no way for a second reviewer to see Claude's proposed changes in Word's Review pane.

For one-off reading tasks, this is fine. For professional document workflows — contract review, policy revision, agreement negotiation — the manual re-entry step is the bottleneck, and it creates the risk of transcription error.

How the Scaffold MCP Connector Gives Claude Full Word Editing Capabilities

The Model Context Protocol (MCP) is an open standard that lets Claude call external tools during a conversation. The Scaffold MCP connector is an MCP server built for Word document operations. When you connect it to Claude, Claude gains three new capabilities: reading a full .docx document with structure intact, applying tracked-change redlines and writing them back into the document's XML, and populating document templates with variable data.

What the Scaffold MCP connector adds to Claude

Without any add-ons, Claude can read text you paste or upload and return revised text in the chat window. With the Scaffold MCP connector installed, Claude can call Scaffold's tools during the conversation: it reads the uploaded document via Scaffold's read_document tool, which returns the full structured content including paragraph hierarchy and section breaks. When you ask Claude to make changes, Claude calls Scaffold's redline_document tool with specific instructions — which text to delete, what to insert in its place, where to add new clauses. Scaffold's server executes the Open XML operations, wrapping deletions in <w:del> elements and insertions in <w:ins> elements with correct author and timestamp metadata. The result is a .docx file that opens in Word with all proposed changes visible in the Review pane, ready for human review, acceptance, or rejection. The AI contributes the legal and editorial reasoning; Scaffold contributes the document engineering that converts those decisions into proper Word markup.

Setting Up Scaffold MCP in Claude

Setup takes about five minutes. You create a Scaffold account at app.scaffoldyourdocs.com/sign-up, get your MCP connection string from the Scaffold dashboard, and add it to Claude Desktop's MCP settings (or claude.ai's connector settings if you are on claude.ai web). Scaffold's setup guide walks through each step.

Once connected, Scaffold is available in every Claude conversation. You do not need to re-connect or re-configure it for each document.

What a Scaffold Redline Conversation Looks Like

Here is a representative example of how a document review conversation flows with the Scaffold MCP connector active:

You upload a vendor MSA to the conversation and type: "Review this agreement and redline it to add a mutual NDA obligation in the confidentiality section, shorten the payment terms from net-60 to net-30, and flag any one-sided indemnification language."

Claude reads the document via Scaffold, identifies the confidentiality section and payment terms clause, proposes specific language, and calls Scaffold's redline tool with those changes. Within the same conversation, Claude returns a message like: "I've applied three changes to your document — here is the download link. The confidentiality section now includes a mutual obligation at paragraph 4.2, payment terms are updated to net-30 in section 7, and I've added an inline comment flagging the indemnification clause in section 11 as one-sided. Please review before accepting."

You download the file, open it in Word, and see every proposed change as a tracked revision — deletions in strikethrough, insertions underlined — exactly as if a human reviewer had marked it up.

Frequently Asked Questions

Can Claude natively edit Word files and produce tracked changes?

No. Claude (without any MCP connector) can read Word documents and return suggested changes as text in the chat, but it cannot produce a .docx file with embedded tracked changes. That requires a tool that bridges the AI's text output and Word's Open XML format. The Scaffold MCP connector is that bridge.

Does this work on claude.ai in the browser, or only in Claude Desktop?

The Scaffold MCP connector works in both environments. Claude.ai on the web supports MCP connectors if you are on a paid Claude plan (Pro or Team). Claude Desktop also supports MCP natively. The workflow and output are identical in both cases.

Is this different from Claude Code?

Yes. Claude Code is a command-line developer tool for writing and editing software code. It is aimed at engineers working in code repositories. The Scaffold MCP connector is for Word document operations — contracts, policies, templates, agreements — and is aimed at legal, HR, consulting, and other document-heavy professionals. The two tools have no overlap.

What does it cost?

Claude requires a paid plan (Claude Pro at around $20/month) to use file uploads reliably and to access MCP connectors on claude.ai. Scaffold has a 7-day free trial, then $29/month for Pro or $29/user/month for Team. The Scaffold connector also works in ChatGPT, so if you already pay for ChatGPT Plus, you can use Scaffold there without adding a Claude subscription.

Does Scaffold work with Word templates, not just existing documents?

Yes. The Scaffold MCP connector supports a template mode where you define variable fields in a Word document and ask Claude to populate them based on your inputs. This is useful for generating first drafts — offer letters, NDAs, engagement letters — where you have a standard structure and variable facts to fill in.

Start a free 7-day Scaffold trial and connect it to Claude in a few minutes. The first time you download a redlined .docx directly from a Claude conversation, the workflow difference is obvious.