MCP server registry
Data & contentPublic source

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.

01

80 tools spanning document lifecycle, reading, writing, formatting, tables, media, math/charts/shapes, and export to PDF / HTML / Markdown / plain text.

02

KDP book formats — create_document accepts kdp:technical, kdp:novel, kdp:cookbook, kdp:children, kdp:interior_design, kdp:encyclopedia, kdp:manga.

03

21 business templates — publication-grade, fully parameterized via a data object (see below).

04

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.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

docx-mcp-server

Validates the request and owns 88 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: rmcp

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_document

Create a new DOCX document. KDP book formats: 'kdp:technical' (6x9), 'kdp:novel' (5.25x8), 'kdp:cookbook' (8x10), 'kdp:children' (8.5x8.5...

local write
list_templates

List business document templates for create_document. Returns 'templates' (each: format id, description, 'data_keys' human summary, and s...

read only
create_novel

Create a professionally-styled novel with author-specific settings (trim size, font, spacing). Sets justified body text, widow control, c...

local write
open_document

Open an existing .docx file from disk

local write
save_document

Save document to disk as .docx

local write
close_document

Close a document and free memory

local write
describe_document

Get document info: paragraph count, table count, word count

read only
insert_paragraph

Insert a paragraph with optional style and page break. Styles: Heading1, Heading2, Heading3, BodyText, BodyTextIndent, ChapterNum, TitleP...

local write
insert_code_block

Insert a syntax-highlighted code block with gray background (Courier New 9pt). Supports 'rust' highlighting.

local write
insert_callout

Insert a callout box with colored background and border (tip=green, warning=orange, note=blue)

local write
add_table

Insert a table at the given position

local write
set_table_cell

Set text in a table cell by table_index (0-based), row, and col.

local write

Governance

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.

71 local write16 read only1 local read
  • 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.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
rmcpRegistry manifest

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.

Install
cargo install docx-mcp-server
MCP client configuration
{
  "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.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
0.1.0
License
Apache-2.0
Tools
88
Revision
38618468a788
Updated
May 31, 2026
Transportsstdio