Safe Docx
Edit existing Word .docx files from your agent without destroying styles, headers, or layout—contracts, specs, and client deliverables.
Overview
Safe Docx is a MCP server for the Build phase that performs surgical, formatting-preserving edits on existing Word .docx files for AI agents.
What is this MCP server?
- Surgical edits on existing .docx with formatting preservation
- AI-native workflow via @usejunior/safe-docx npm MCP v0.9.1
- stdio transport with npx runtime hint
- Published tooling site at usejunior.com/developer-tools/safe-docx
- Monorepo subfolder packages/safe-docx on GitHub
- Version 0.9.1, npm identifier @usejunior/safe-docx
- stdio MCP transport; website usejunior.com/developer-tools/safe-docx
- Repository: github.com/UseJunior/safe-docx (packages/safe-docx)
Community signal: 32 GitHub stars.
What problem does it solve?
Pasting docx content into chat flattens styles and breaks client-ready Word deliverables.
Who is it for?
Solo builders and consultants who ship .docx contracts, specs, or reports and want agent edits without rebuilding templates.
Skip if: Teams that only author docs in Markdown or Google Docs with no Word template requirements.
What do I get? / Deliverables
Your agent can apply targeted .docx edits through MCP while preserved formatting survives for legal, spec, and proposal documents.
- Updated .docx files with preserved formatting after agent edits
- Repeatable MCP workflow for contract and spec revisions
- Reduced manual Word editing for client-facing documents
Recommended MCP Servers
Journey fit
Document surgery happens during build when you produce or revise formal docs, SOWs, and handoff packages alongside code. Docs is the canonical shelf for MCP tooling focused on structured authoring and revision of written deliverables.
How it compares
Formatting-aware docx MCP editor, not a generic file-write skill or PDF converter.
Common Questions / FAQ
Who is io.github.UseJunior/safe-docx for?
Indie builders, freelancers, and small teams that deliver Word documents and want MCP-driven surgical edits with styles intact.
When should I use io.github.UseJunior/safe-docx?
During build and docs work when you must revise an existing .docx—contracts, proposals, or specs—not when creating net-new Markdown READMEs only.
How do I add io.github.UseJunior/safe-docx to my agent?
Install @usejunior/safe-docx, configure stdio MCP (npx per registry), and point your agent at the server before opening target .docx paths in tool calls.