← Back to directory
S

Safe Docx MCP Server

Community
AI-native surgical editing of Word and OpenDocument files with formatting preservation
GitHub source repository ↗
★ 37 Stars Category · Filesystem Popular
68FMRS · C

Safe Docx is a local, stdio-based MCP server (npm-distributed, Apache-2.0) built for coding agents, offering surgical, format-preserving edits to .docx/.odt files with conformance evidence for OOXML compatibility. It is not suited as a visual editor or collaboration tool.

Reliability
8/20
Security and permissions
16/20
Maintenance
14/20
Documentation
18/20
Setup experience
12/20
Read the FMRS scoring method →

Safe Docx is a local MCP server and CLI for reading, searching, editing, comparing, converting, and saving .docx and .odt files. Distributed via the npm package @usejunior/safe-docx over stdio, it preserves document structure and can produce clean or tracked-changes output. The project is Apache-2.0 licensed and publishes ECMA-376 / OOXML conformance reports. No tool names are listed in the source material, so the tool list is left empty.

Setup

Install globally with npm install --global @usejunior/safe-docx, then configure your MCP client with the installed executable's absolute path. For Claude Code: claude mcp add safe-docx -- /absolute/path/to/safe-docx.

Fit and risk

Best for

  • Developers who need precise, format-preserving edits to .docx/.odt files via coding agents
  • Workflows that require tracked-changes output for human review

Not for

  • Visual editing scenarios needing browser rendering, real-time collaboration, or pixel-level pagination guarantees
  • Using .dotx templates directly (they must be converted to .docx first)

Required permissions

  • Filesystem access to read and write local .docx / .odt documents

Risks and side effects

  • Edits apply to local files; incorrect targeted changes could overwrite original content — use the clean/tracked-changes dual output for review
  • The project is not a visual editor or layout engine, so complex layout results should be verified manually

Troubleshooting

  1. Verify the npm package is globally installed and the client uses the executable's absolute path
  2. Ensure .dotx templates were converted to .docx before use
  3. See docs/installation.md in the repository for version pinning and client configuration

Use cases

Have a coding agent make targeted edits to a .docx (e.g., change the governing-law clause in an NDA) and save both clean and tracked-changes copies
Search, compare, and convert Word / OpenDocument files