docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_contents_from_docxA | Read a paginated batch of content blocks (paragraphs and tables) from a .docx file. Returns items, total, offset, limit, and has_more — loop with increasing offset until has_more is false. Blocks carry style name references only; use get_styles_from_docx for full style definitions. |
| write_contents_to_docxA | Write content blocks to a .docx file. Creates a new file if the path does not exist; replaces the document body if it already exists. Pass blocks collected from get_contents_from_docx. Call before write_styles_to_docx when reformatting. |
| get_styles_from_docxA | Read a paginated batch of paragraph style definitions from a .docx file. Returns paragraph_styles, total, offset, limit, and has_more. The section field (page size and margins) is included only in the first batch (offset=0). Merge all batches client-side before calling write_styles_to_docx. |
| write_styles_to_docxA | Union paragraph style definitions onto an existing .docx file. The target file must already exist — call write_contents_to_docx first. Incoming styles win on name conflict. Pass a StyleProfile dict with paragraph_styles and optional section from get_styles_from_docx batches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a unique and clearly distinct purpose: reading content, reading styles, writing content, and writing styles. No overlap or ambiguity.
All tools follow a consistent verb_from_docx or verb_to_docx pattern with snake_case, making it predictable and easy to understand.
With 4 tools covering the core read/write operations for docx contents and styles, the scope is well-defined and each tool earns its place.
The tool set provides full coverage for reading and writing both contents and styles of docx files, with no obvious gaps for the stated purpose.