# adeu [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/dealfluence/adeu  
**GitHub Stars:** 170  
**npm Downloads (last month):** 5652  
**Views:** 15  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/adeu

## Description
docx ↔ LLM translator. Projects .docx office files to Markdown for editing. Projects edits back to OOXML as tracked changes (redlines). Python and Node.js implementations.

## Tools
Capabilities this server exposes over MCP:

- **accept_all_changes** — Accepts every tracked change in the document, producing a finalized clean document.

remove_comments (boolean, DEFAULT TRUE): also delete every comment. The default is TRUE because this tool's purpose is a distributable clean document, and comments are internal review notes that must not travel to a counterparty. Pass remove_comments=false to accept the tracked changes while KEEPING the comments — use that when the review conversation is still live. Either way the response reports how many comments were deleted and names each one with its author, and comments whose anchored text an accepted deletion consumes are removed regardless, exactly as Word does. [Adeu v3.2.1+b7aad81]
- **apply_text_revision** — Applies whole-text revised text to a DOCX document by computing a diff and generating tracked changes. Includes a clean-text verification gate to ensure the applied document matches the supplied text.

`revised_text` must be the complete CLEAN view of the document: read it with `read_docx` (`clean_view=true`, `page='all'`), edit that text, and send ALL of it back. Never CriticMarkup ({++, {--, {>>) — this tool diffs against the clean view, so markup tokens would land in the document as literal prose. Never one page of a paginated extract — everything absent from the text is applied as a tracked deletion.

INTERLOCK: a revision that drops >50% of the characters (>75% for documents under 2000 characters) is refused unless you pass allow_major_deletions=true.

If the applied document's clean text does not then match `revised_text`, NOTHING is written to output_path: a diagnostic copy is kept at <name>.unverified.docx and the call fails. output_path defaults to <name>_redlined.docx; an existing _redlined/_processed artifact is revised in place. [Adeu v3.2.1+b7aad81]
- **diff_docx_files** — Compares two DOCX files and returns a compact `@@ Word Patch @@` diff — Adeu's token-level, sub-word patch format — of their text content. Useful for analyzing differences between versions before editing.

Pass `output_path` (and optional `author_name`) to also write the comparison as a tracked-changes .docx of original_path in one step — the recommended way to make a redline between two versions; never hand-build compare batches. All or nothing: if any change cannot be tracked, nothing is written. output_path may not be either input. [Adeu v3.2.1+b7aad81]
- **finalize_document** — Prepares a document for external distribution or e-signature. Note: in this zero-dependency environment, protection_mode='encrypt' is unsupported and falls back to a native read-only lock; export_pdf and password are ignored. [Adeu v3.2.1+b7aad81]
- **process_document_batch** — Applies a batch of edits and review actions to a DOCX.

Batches apply SEQUENTIALLY: each change validates against state from prior changes. Valid changes apply when others fail (salvage default): response LEADS with `PARTIAL: applied K of N` listing unapplied changes. Pass partial=false for all-or-nothing.

Each item in `changes` needs a `type`:
1. 'modify': search-and-replace. `target_text` must match uniquely (`match_mode`:'strict', default) — add context or set `match_mode`:'first'/'all' or `regex`:true ($1, $2… in `new_text`). `new_text` supports '#'–'######' headings, '**bold**', '_italic_', '\n\n' splits, and pipe tables (`| H1 | H2 |\n|---|---|\n| A | B |`). Omit `new_text` (with `comment`) to annotate; empty string deletes. Never write CriticMarkup — use `comment` (string or `[{text, author?}]`).
   • EMPTY CELLS: blank cells carry `{#cell:<id>}` anchors — set `target_text` to the anchor and value in `new_text`.
2. 'accept'/'reject': finalize or revert by `target_id` ('Chg:12'); add `part` ('word/header1.xml') when the id exists in several parts.
3. 'reply': reply to `target_id` ('Com:5') with `text`.
4. 'set_field': fill a form field — `field` is 'CC:<N>', tag or alias, `value` the text (list via `read_docx` `mode`:'fields'; checkboxes true/false, dates YYYY-MM-DD, dropdowns a listed option). Updates bound stores; locked/protected controls refuse and name the override.
5. 'insert_row': add table row (`target_text` anchor, `cells` array left-to-right, `position` 'above'/'below'). 'delete_row': remove row matching `target_text`. Disk mode only.

ID VOLATILITY: 'Chg:N'/'Com:N' shift between states — call `read_docx` before accept/reject/reply.

`markup_mode`:'manual' writes strikethrough/underline + comments instead of Track Changes.
`author_name` sets attribution; default 'Adeu AI (TS)'. [Adeu v3.2.1+b7aad81]
- **read_docx** — Reads a DOCX file. Returns text with inline CriticMarkup for Tracked Changes and Comments: {++inserted++}, {--deleted--}, {==highlighted==}{>>comment<<}. Set clean_view=True for the finalized 'Accepted' text without markup.

Modes:
- 'full' (default): paginated body content. Use page=N to navigate.
- 'outline': heading map only — start here for large docs to plan targeted reads. Defaults to L1-L2 headings; pass outline_max_level=3-6 to see deeper structure.
- 'appendix': defined terms, anchors, and cross-reference targets. Consult before editing legal/technical docs to avoid breaking references.
- 'changes' (mode='changes'): a ledger of every tracked change and comment (id, type, author, page, snippet) — start here for review work instead of reading pages. Filter with changes_author, page, and changes_offset.
- 'fields' (mode='fields'): a ledger of every content control (ordinal, class, alias/tag, location, lock/binding state, current value) — start here to discover fillable fields. Paginate with fields_offset; `page` and `search_query` do not apply.

`page`: a positive integer (1-indexed, default 1), a page RANGE like '2-6' (returns up to 8 pages in one call, then names the next range), or 'all'. Pages are synthetic length-based chunks sized for LLM consumption, NOT printed Word pages. In mode='full', page='all' returns the whole body with no page chrome; when over the response budget, it serves the first pages that fit plus an L1 outline and continuation hint unless force=true. With `search_query`, `page` instead restricts matches to that page or 'N-M' page range (default: search all pages). [Adeu v3.2.1+b7aad81]

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "adeu": {
    "command": "npx",
    "args": ["-y","@adeu/mcp-server"]
  }
}
```

## Documentation

## What adeu MCP server does

The adeu MCP server provides an MCP interface for reading and modifying Microsoft Word `.docx` files. It projects document content into an LLM-readable representation and converts approved edits back into DOCX tracked changes. This lets an agent work with document text without directly manipulating WordprocessingML.

The server is intended for review and editing workflows where the original document structure, formatting, comments, and revision history matter. It can read clean text or expose tracked changes and comments through CriticMarkup. It also supports document finalization, comparison of two files, content-control fields, and table-row operations.

## How it works

Use `read_docx` to inspect a document. The tool supports full text, heading outlines, appendices, tracked-change and comment ledgers, and content-control field listings. Full reads can be paginated, searched, or requested as a complete clean view. Pages are synthetic chunks for model consumption rather than printed Word pages.

For targeted edits, `process_document_batch` applies a sequence of modifications and review actions. Modify operations can replace uniquely matched text, use first or all matches, apply regular expressions, add comments, or insert Markdown-style headings and emphasis. Other operations accept or reject tracked changes, reply to comments, fill fields, and add or remove table rows. Batch processing can salvage valid changes when others fail, or run in all-or-nothing mode.

`apply_text_revision` accepts the complete clean text and computes tracked changes against the existing document. It verifies that the resulting clean text matches the supplied revision and blocks large deletions unless explicitly allowed. `diff_docx_files` returns a compact token-level Word Patch comparison, while `accept_all_changes` produces a finalized document with tracked changes accepted.

## Setup and configuration

The adeu MCP server can run through either the Node.js package or the Python package. A JSON MCP configuration can use `npx -y @adeu/mcp-server` for Node.js or `uvx --from adeu adeu-server` for Python. The Python backend is required for live editing of an active Microsoft Word document on Windows.

Claude Desktop also supports installation through the released `Adeu.mcpb` extension package. Claude Code can use the published plugin and optionally connect to either MCP backend. Gemini CLI provides an extension installation command, and the repository documents a skills-based installation for compatible agents such as Cursor, Windsurf, and VS Code Copilot.

## Tools and capabilities

The adeu MCP server exposes tools for:

- Reading document text, outlines, appendices, revisions, comments, and fields.
- Applying validated text revisions and sequential batches of edits.
- Accepting or rejecting tracked changes and removing comments.
- Replying to comments and setting content-control field values.
- Inserting or deleting table rows in disk-based documents.
- Comparing DOCX files with a compact token-level diff.
- Finalizing documents for external distribution or e-signature.

## Limitations and notes

`apply_text_revision` requires the entire clean document text, not a paginated fragment or manually inserted CriticMarkup. Large deletion requests are refused by default under the documented thresholds. Change and comment identifiers can shift after document state changes, so read the current ledger before acting on an identifier.

In the zero-dependency environment, `finalize_document` does not support encrypted protection. Its read-only lock fallback is used instead, and `export_pdf` and password options are ignored. Existing content-control locks may also prevent field updates unless an applicable override is provided.

_Full upstream README: https://allmcps.com/mcp/adeu/readme_

