Everything plus the kitchen sink for Microsoft Word: the most complete .docx MCP server ever plumbed.
This is the last Word MCP server you will need to install. Nothing else in the category comes close on capability: 221 operations reach every part of a Word document that serious work touches, and the survey further down this page is mostly empty columns. Completeness is only half of it. Your documents stay open in Word while the agent edits them, so each change appears in the window in front of you rather than arriving as a file you have to reload, and there is a backup before every change, made without you asking. Nothing you have written gets lost here.
A committee returns the manuscript covered in tracked revisions, and the citation apparatus has to survive the rewrite. The scholarly furniture that other tools trample, from footnotes to the reference list, is first-class here, so an agent can take on the revision pass without breaking any of it.
Contracts, policies, and case files live in Word, and every edit needs an author attached. Edits here can be written as tracked changes, comparing two versions works the way Word itself does it, and redaction actually removes the text, then verifies that it is gone.
For anyone whose documents are too important to gamble with. Watch the edit land in your own open Word window, take it back with a single Ctrl+Z if you don't like it, and know there was a backup before anything was touched. You keep the cursor; the agent does the typing.
What 2.1.0 just added
The whole list, no release notes required.
An AI agent once needed fifteen minutes to edit twenty table cells in a Word document. Not because the agent was slow, but because every Word MCP server on the market was missing something. One couldn't delete a table column. Another had no footnotes. A third couldn't touch a table of contents. Installing all three still couldn't do the job.
So instead, this got built: one server with everything. The twenty-cell edit now takes one call and finishes in twenty milliseconds. Your agents will simply never know the struggle.
The stock is arranged in capability packs, the way a good hardware store is arranged in aisles. Browse the shelves below; your agent only carries an aisle when the job calls for it.
Merge-aware column insert/delete, one-call bulk cell edits, merge/unmerge, gridBefore rows, nested tables, sort, split, named styles, header repeat.
e.g. add a column to a table full of merged cells · rewrite twenty cells in one call · sort a table by any column
media-forms · liteNative citations & bibliography (12 styles, verified Word rendering), footnotes & endnotes with conversion, index generation, TOC & caption lists, cross-references.
e.g. insert a citation and build the bibliography · convert every footnote to an endnote · refresh the table of contents
references · academicWrite edits AS tracked changes, accept/reject by author, Word-native document compare, two-reviewer combine, threaded comments with resolve.
e.g. write an edit as a tracked change under a chosen author · accept only one reviewer's changes · list every comment with its context
reviewFragmented-run-safe find/replace with ReDoS guards, character & paragraph formatting long-tail, custom styles, template transfer, change-case, lists.
e.g. replace a phrase Word split across formatting runs · restyle every heading level in one pass · copy styles in from another document
lite · academicHeaders/footers, roman-numeral page formats, line numbering, watermarks, multi-column sections, margins, images with alt text, Page X of Y.
e.g. switch front matter to roman numerals · add a DRAFT watermark · put Page X of Y in the footer
academicMove entire sections (heading + content + tables), chapter merge, document properties, protection with Word-compatible SHA-512 password hashing.
e.g. move a whole section with its tables · merge chapters into one file · password-protect the result
assembly · protection-ioPer-section word counts, APA citation-parity checking, Word's own proofing errors & readability statistics, structural validation.
e.g. count words per section · check citations against the reference list both ways · pull Word's own readability statistics
academicCOM-backed field refresh (real TOC page numbers), PDF export, encrypted save, open-clean validation, live-Word status and lock management.
e.g. refresh TOC page numbers with real pagination · export a PDF · confirm the file opens with no repair prompt
com-liveEdit documents while they are OPEN in Word: changes appear in the window, each tool call is one Ctrl+Z step, the cursor is never touched. Cursor-point insert, scroll-to-show, track-changes toggle, crash repair.
e.g. insert text at the cursor while the document is open · scroll the window to what changed · toggle track changes mid-session
com-liveMail merge from CSV/JSON, batch operations across document sets, true redaction with verification, accessibility & template-compliance audits, cross-reference and caption validation, submission prep, front-matter assembly, chapter headers, structural diagnostics, PDF import.
e.g. run a mail merge from a CSV · redact a name and verify it is gone · audit a report for accessibility
assembly · academicLaTeX equations as native Word math, Zotero library citations, publication style conversion across eight styles, review-cycle analytics, journal word counts, peer-review anonymization, table data round-trips, document splitting.
e.g. turn LaTeX into native Word equations · cite straight from a Zotero library · anonymize a manuscript for peer review
references · media-formsTool counts flatter everybody. What matters is what happens when you actually ask:
| Capability | 🚰 KitchenSink4Word | word-mcp-live | GongRzhe (archived) | docx-mcp (SecurityRonin) | Official add-ins* |
|---|---|---|---|---|---|
| GitHub stars† | 5 | 202 | 2.1k | 45 | n/a |
| Native citations & bibliography | ✔ 12 styles | ✘ | ✘ | ✘ | n/d |
| Citation style conversion (APA/Chicago/Turabian/MLA…) | ✔ 8 styles | ✘ | ✘ | ✘ | n/d |
| Tracked-changes authoring (writes edits as revisions) | ✔ | ✔ | ✘ | ✔ | ✔ |
| Footnote/endnote conversion | ✔ both directions | ✘ | ✘ | ✘ | n/d |
| TOC insert + refresh | ✔ | ✘ | ✘ | ✘ | n/d |
| Index generation | ✔ | ✘ | ✘ | ✘ | n/d |
| Document protection | ✔ Word-compatible SHA-512 | n/d | n/d | n/d | n/d |
| Mail merge | ✔ | ✘ | ✘ | ✘ | n/d |
| Accessibility audit | ✔ | ✘ | ✘ | ✘ | n/d |
| Equations (LaTeX to Word math) | ✔ | n/d | ✘ | n/d | n/d |
| Zotero integration | ✔ | ✘ | n/d | n/d | n/d |
| Works without Word installed | ✔ file tools; COM optional | n/d | n/d | ✔ | ✘ |
| Live editing while open in Word | ✔ one Ctrl+Z per call | ✔ | ✘ | ✘ | ✔ in-app |
| Tiered context loading (lite core, packs on demand) | ✔ | ✘ | ✘ | ✘ | n/d |
| Anti-corruption evidence (tests / corruptions) | ✔ 1,842 / 0 | n/d | n/d | n/d | n/d |
Capability survey as of 2026-08-28, compiled from public repositories, documentation, and issue trackers. n/d: not documented in the sources surveyed (not a claimed absence). * Official add-ins covers Microsoft's Word AI offerings and the Claude for Word add-in: cloud-based or Team/Enterprise scoped, not local MCP servers. Corrections welcome: open an issue. † Star counts read from the GitHub API on 2026-09-04, shown for context: stars say how long a project has been in view, not what it can do.
Every MCP server takes a bite out of your assistant's memory before any work starts, and a big bite has a cost you can feel: an assistant that forgets what you told it ten minutes ago. Almost nobody tells you the size of the bite. Here is ours, measured: small to start, growing only when a task needs a specialty pack, and the exact numbers are on the tiles below.
The measured bill: about 8,000 tokens to start, about 27,800 with every pack on, down from about 34,400 in v1.6.
MORE REACH, FEWER TOOLS · v1.6 measured 200 operations across 189 tools; v2.0 delivers 221 across 110. Measured with one yardstick on both versions, so the comparison holds.
TIERED LOADING · Shipped. A session starts on the 29-tool lite core and turns on packs with one enable_tools call. Starts lite, the whole sink one call away.
Pick the line that describes you. Most people are the first one.
Download the installer bundle from the latest release and double-click it, or drag it into the Claude Desktop window. Desktop adds it as an extension and the sink is connected. Nothing to type, nothing to configure.
Download the .mcpb bundle →One-time requirement: uv on your PATH, which the bundle uses to start the server.
One line in a terminal and you are done. It fetches and runs the server for you, so there is nothing to install first.
In Claude Desktop's Tool permissions for this server, set the Read-only tools group to Always Allow. Those tools cannot change anything, so approving them once is safe, and Claude stops asking about every read. Leave the acting tools on Ask, so anything that changes things still checks with you first.
Install the package and point any MCP client at the executable:
Then in any client's config: {"mcpServers": {"word": {"command": "kitchensink4word"}}}. Running from a clone works the same way; point the command at the word-mcp executable in the clone's virtual environment. Full setup, including the sandbox options, is in the README.
Windows. File-based tools need no Word installation; the Word-app tools (TOC refresh, PDF, proofing…) use a local Microsoft Word.
Something glitched, refused, or misbehaved. File a report at the repair counter: the form asks exactly what a fix needs. Never attach a private document; rebuild the structure with placeholder text.
File a bug report → 🚿A Word capability the sink should also have. Describe the real task behind it and it goes on the workbench.
Request a feature → 💼Free for individuals and personal use, and it stays that way. If your company wants to build it into a product of its own, that needs a commercial license, with terms worked out case by case. This counter is where you start that conversation.
Arrange a license →Reports are public GitHub issues (a free GitHub account is needed to file one). Every report lands in the maintainer's inbox.
You know the morning: the manuscript is due, Word opens, and there is a dialog offering to "repair" your file. That morning is what this whole server is built to prevent. Before any change, a backup is made automatically. Every save is checked before it replaces your file, so a bad write cannot take the original with it. And everything the edit doesn't touch, from equations to textboxes, passes through exactly as it was, byte for byte. Two full stress campaigns and a shelf of long, heavily formatted real manuscripts, and Word has never once offered to repair anything this server saved.
Provided as-is, without warranty of any kind, per the license; the engineering above is simply how seriously your documents are taken. Keep backups. (It makes them for you.)
Everything plus the kitchen sink for Microsoft PowerPoint. Move the node, the arrows follow: diagrams your hands can still move. Tables that behave, and the same never-corrupts promise, now for slides.
Visit the paint aisle → 🔌Everything plus the kitchen sink for Excel (.xlsx): every value labeled calculated, cached, or missing, so the AI never repeats a stale number as a fresh one. Same never-corrupts promise, now for spreadsheets.
Visit the electrical aisle → 🪴Everything plus the kitchen sink for the web: budgeted page reads that name what went unread, structured extraction with named evidence, and a consent ladder that cannot be talked into payments. Read-only out of the box.
Visit the garden aisle → 🏪The whole hardware store on one page: every KitchenSink server, its fixture, and its counter, plus a shelf or two that are not empty by accident.
Browse the store →