Word AI MCP server

Word AI

<!-- mcp-name: io.github.flyfish-dev/word-ai -->

Structure-preserving Word (DOCX) editing for AI agents.

Word AI is an open-source MCP server and Office.js bridge for safe, auditable, incremental editing of Microsoft Word documents. It is designed for Codex, OpenAI Agents, and other MCP clients that need to edit .docx files without rebuilding the document or damaging styles, numbering, tables, images, fields, headers, footers, and relationships.

Why Word AI

AI systems are good at generating text, but Word documents are structured packages. A naive DOCX-to-Markdown-to-DOCX workflow can break numbering, styles, tables, images, fields, references, and layout. Word AI keeps the original DOCX structure as the source of truth:

• Agents generate constrained PatchSet operations.
• The local engine applies targeted OOXML/Open XML edits.
• Every write goes through assessment, dry-run, backup, validation, audit, and diff.
• The Office.js add-in provides a Word taskpane for anchor governance and human-in-the-loop workflows.

Key Features

• 63 MCP tools for DOCX inspection, anchors, headings, paragraphs, tables, fields, images, comments, revisions, PatchSet planning, dry-run, apply, validation, rollback, diff, live Word session editing, and optional read-only OfficeCLI evidence.
• PatchSet-only writes. No full document rebuilds, no Markdown/HTML round-trips, and no direct source overwrite by default.
• Agent-friendly PatchSet normalization for common aliases such as operation, targettag, newtext, text_sha256, and camelCase operation names, while preserving the canonical safety gates.
• Content-control first editing using stable Word content control tags such as WORD-AI:SRS:1.0:overview.
• Strong preconditions with sourcesha256, expectedoldsha256, and expectedold_text.
• Structure validation for package parts, content controls, tables, paragraphs, fields, comments, images, revisions, and protected body blocks.
• Python MCP facade and bridge runtime for local agent integration, path policy, session queues, and distribution compatibility.
• .NET 8 Open XML SDK engine as the authoritative offline DOCX transaction backend, using a packaged native binary or Release DLL when available.
• Single-file standalone binaries and quickstart bundles for no-clone, no-venv, no-.NET-SDK offline DOCX editing and one-command Agent Skill installation.
• Office.js taskpane for Word-side anchors, PatchSet preview, dry-run, apply, and open-document content-control editing with hash checks.
• Live Word session tools (wordsession) so Codex can read, preview, apply, and roll back edits in the currently open Word document through Office.js.
• Local HTTP bridge secured by a local token and localhost-only CORS for Office add-in workflows.

Architecture

Codex / Agent / MCP Client
        |
        v
Word AI MCP Server
        |
        +--> Python MCP facade / read indexes / Office bridge
        +--> .NET Open XML SDK backend for offline PatchSet transactions
        +--> Office bridge HTTP API
        +--> File-backed Word session command queue
        |
        v
Original DOCX -> PatchSet -> Candidate DOCX -> Validation -> Output DOCX + Audit JSON + Diff

The Office.js taskpane is the Word session layer. It creates and lists content controls, connects to the local bridge, registers the current Word document as a live session, polls commands queued by Codex, executes supported PatchSet operations through Office.js, and returns audit/rollback data.

Quick Start

Use the most native distribution path your agent host supports:

Shortened. The full README is on GitHub.