Everything plus the kitchen sink. And yes, it just works.
A FAMILY OF MCP SERVERS · ONE FIXTURE PER DEPARTMENT · AGPL-3.0
The most complete Word (.docx) MCP server ever plumbed. Live editing of open documents, native citations and bibliography, merge-aware table surgery, footnotes, tracked-changes authoring, redaction with verification. Engineered not to corrupt.
221 operations · 110 tools · 1,842 tests · 0 corruptions
Everything plus the kitchen sink for PowerPoint (.pptx), headlined by the fixture nobody else carries: SVG in, grouped native shapes with glued connectors out. Move the node, the arrows follow. Plus the first file-based structural table surgery, slide management done right, and tiered loading from day one.
159 operations · 141 tools · 1,241 tests · 0 corruptions
Everything plus the kitchen sink for Excel (.xlsx), headlined by the thing every other server gets wrong: a spreadsheet remembers its answers, not its thinking, so a stale number looks exactly like a live one. This one labels every value it hands back, names the cells that went stale, and asks Excel itself to recalculate when it matters. Structural edits carry their formulas with them. Tiered loading from day one.
129 operations · 69 tools · 1,294 tests · 0 corruptions
Everything plus the kitchen sink for the open web: your AI reads whole pages for the price of a paragraph, shadow roots included, and cannot click a thing until you flip the switch. Every read ends with the price it paid and a list of what it skipped.
19/52 tools · 2,065 tests · 7× cheaper reads · 0 acting tools until allowed
KitchenSink4PDF
Backordered. This shelf is not empty by accident.Came in for one and want the set? It all fits in one cart.
Claude Code, paste once and the register rings up all four:
claude mcp add word -s user -- uvx kitchensink4word
claude mcp add ppt -s user -- uvx kitchensink4ppt
claude mcp add xl -s user -- uvx kitchensink4xl
claude mcp add web -s user -- uvx kitchensink4web
Developers:
pip install kitchensink4word kitchensink4ppt kitchensink4xl kitchensink4web
Nobody wants to install a tool for a job that comes up once. The one time the job does come, though, nobody has the hours to go find the tool either. So these shelves hold everything, including things you may never touch, and the day you need one, it is already there. Everything on them is built to the same house standard: a backup lands before your file changes, the work is checked after, and when something cannot be done, your AI says so plainly instead of guessing. The spec sheets hang in each aisle.
One server per document format, complete enough that your agent never has to shop anywhere else.
Atomic validated saves, automatic backups before every change, byte-identical passthrough of everything untouched, and adversarial test evidence published with every release.
When a target is ambiguous, the tools refuse and show the candidates. A confident wrong edit is the one product this store does not stock.
Sink acting up?
Leaks, missing attachments, and feature requests for KitchenSink4Word all go to the plumbing desk. Structured forms ask exactly what a fix needs; never attach a private document, rebuild the structure with placeholder text.
Visit the Word service desk → AISLE P · PAINT 🎨Streaks in the finish?
Glitches, refusals, and feature requests for KitchenSink4PPT go to the paint desk. Same structured forms, same house policy; never attach a private deck, rebuild the structure with placeholder text.
Visit the PPT service desk → AISLE X · ELECTRICAL 🔌Found a number you can't trust?
A value labeled wrong, a refusal that made no sense, a save that touched something it shouldn't have, or a capability the sink should have and doesn't. File it at the counter: the forms ask exactly what a fix needs. Never paste real spreadsheet data; describe the shape of the workbook instead.
Visit the Excel service desk → AISLE G · GARDEN 🪴Weeds in the garden?
Overgrown pages, surprise costs, and feature requests for KitchenSink4Web go to the garden desk. Same structured forms, same house policy; never paste a private page, describe its shape instead.
Visit the Web service desk →Commercial fitting? Free for individuals and personal use, and it stays that way. If your company wants to build one of these servers into a product of its own, that needs a commercial license, and terms are worked out case by case. Open an issue at the desk of the product you need and we will talk it through.
Reports are public GitHub issues (a free GitHub account is needed to file one). Every report lands in the maintainer's inbox.
Something broke, something you wish these could do, or your company wants to build them into a product of its own. Whatever brought you to the counter, it is the same window: file it on GitHub and it gets read by the person who built the shelves.