Adeu

Automated DOCX Redlining Engine

Adeu is an MCP server published as the npm package @adeu/mcp-server (version 1.7.1) and communicates over the stdio transport. Its stated purpose is automated redlining of DOCX files — that is, programmatic generation of tracked changes or revision markup within Word-compatible documents.

No tool list is provided in the registry record, so the specific operations an agent can invoke — such as inserting tracked changes, accepting or rejecting revisions, or comparing document versions — cannot be enumerated from verified facts. What is known is that the server is oriented around DOCX document revision workflows, meaning agents that need to handle contract edits, legal markups, or collaborative document review cycles in a Word-compatible format are the target audience.

The server runs via stdio, so it must be launched as a subprocess by the MCP host rather than reached over a network socket. There are no documented environment variables required for configuration. The package is available on npm and the source repository is hosted at github.com/dealfluence/adeu.

Adeu is the wrong choice if the documents in question are not in DOCX format, if a network-accessible transport is required, or if detailed tool-level documentation is needed before integration, since no tool schema is currently published in the registry record.

Use cases

  • Automate redline generation on DOCX contract drafts within an AI agent workflow
  • Produce tracked-change markup in Word-compatible files without manual editing
  • Integrate DOCX revision workflows into document review pipelines
  • Process legal or business documents that require auditable change history

When to use it

  • The documents being processed are in DOCX format
  • A stdio-based MCP server fits the host environment
  • The workflow requires automated generation of redlines or tracked changes
  • The agent pipeline involves contract or legal document review

When not to use it

  • Documents are in PDF, plain text, or formats other than DOCX
  • A network transport (HTTP, SSE) is required rather than stdio
  • Detailed tool-level API documentation is needed before committing to integration, as none is published in the registry record
  • The task is general document editing rather than redlining or revision markup