Adeu MCP Server

Automated DOCX Redlining Engine. Exposed over MCP by the adeu mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Adeu is a docx ↔ LLM translator: a Model Context Protocol (MCP) server (Python and Node.js implementations) and accompanying SDKs that act as a Virtual DOM for Microsoft Word. It provides a two-way abstraction layer that lets AI agents freely edit document text without destroying the underlying formatting or complex DOCX XML.

Its toolset

Everything the assistant can do here goes through one of these:

• Smithery — To install Adeu using the Smithery package manager: bash npx -y @smithery/cli install adeu --client claude

Adding it to your client

@adeu/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Adeu's toolset — Smithery — is a fair guide to whether it matches your workflow. It is maintained by ai.adeu; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the adeu mcp server does with a few real requests.