80 tools spanning document lifecycle, reading, writing, formatting, tables, media, math/charts/shapes, and export to PDF / HTML / Markdown / plain text.
docx-mcp-server
80 MCP tools for creating, reading, editing, formatting, and converting Microsoft Word (.docx) documents — plus KDP book layouts and a library of 21 parameterized business templates. Pure Rust, local-first, no Microsoft…
What it gives an agent
A purpose-built capability behind one MCP connection.
The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.
KDP book formats — create_document accepts kdp:technical, kdp:novel, kdp:cookbook, kdp:children, kdp:interior_design, kdp:encyclopedia, kdp:manga.
21 business templates — publication-grade, fully parameterized via a data object (see below).
Discovery — list_templates returns every template's structured data_fields (name + type + item shape) and the universal style_params, so an agent can learn the schema programmatically.
Architecture
How docx-mcp-server fits into an agent system.
The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.
ADK-Rust agent
Chooses a capability from the reviewed tool catalog.
MCP client
Discovers schemas, sends calls, and receives typed content.
docx-mcp-server
Validates the request and owns 88 documented tool contracts.
Domain system
Keeps the API, data, credentials, and business rules behind the server.
This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.
Tool catalog
What can an agent ask docx-mcp-server to do?
Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.
60 named tools shown from 88 documented tools
create_documentCreate a new DOCX document. KDP book formats: 'kdp:technical' (6x9), 'kdp:novel' (5.25x8), 'kdp:cookbook' (8x10), 'kdp:children' (8.5x8.5...
local writelist_templatesList business document templates for create_document. Returns 'templates' (each: format id, description, 'data_keys' human summary, and s...
read onlycreate_novelCreate a professionally-styled novel with author-specific settings (trim size, font, spacing). Sets justified body text, widow control, c...
local writeopen_documentOpen an existing .docx file from disk
local writesave_documentSave document to disk as .docx
local writeclose_documentClose a document and free memory
local writedescribe_documentGet document info: paragraph count, table count, word count
read onlyinsert_paragraphInsert a paragraph with optional style and page break. Styles: Heading1, Heading2, Heading3, BodyText, BodyTextIndent, ChapterNum, TitleP...
local writeinsert_code_blockInsert a syntax-highlighted code block with gray background (Courier New 9pt). Supports 'rust' highlighting.
local writeinsert_calloutInsert a callout box with colored background and border (tip=green, warning=orange, note=blue)
local writeadd_tableInsert a table at the given position
local writeset_table_cellSet text in a table cell by table_index (0-based), row, and col.
local writeGovernance
Understand the effect of every tool.
A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.
- The registry manifest declares local write, read only, local read tool risk classes.
MCP surface
What the current documentation declares.
MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.
Install and connect
Follow the project’s documented starting point.
Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.
cargo install docx-mcp-server{
"mcpServers": {
"docx": {
"command": "docx-mcp-server"
}
}
}Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.
Official documentation
Continue with the project maintainers’ source of truth.
This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.
Keep exploring
More in data & content.
Source record
Release and repository metadata for this catalog entry.
- Version
- 0.1.0
- License
- Apache-2.0
- Tools
- 88
- Revision
- 38618468a788
- Updated
- May 31, 2026