DOCX MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docx-getSchemaA | Get the JSON schema for DOCX document structure. IMPORTANT: Always call this first to understand the document format before using other tools. |
| docx-createA | Create a new docx from JSON, returns an id. Use docx-getSchema first to understand the required JSON structure. Supports images via 'data' (base64), 'path' (local file), or 'url' (remote image with fallback). |
| docx-openC | Open a .docx file from disk into memory and return id. |
| docx-queryMetaC | Get docx metadata by id. |
| docx-queryObjectsC | List top-level object info by id. |
| docx-editMetaC | Patch metadata of a docx by id. |
| docx-editContentB | Replace a block at index. Use docx-queryObjects first to see available blocks, and docx-getSchema to understand block structure. |
| docx-insertContentA | Insert a block at index. Use docx-queryObjects first to see current structure, and docx-getSchema to understand block structure. |
| docx-removeContentC | Remove a block at index. |
| docx-saveC | Persist the docx to disk path by id. |
| docx-openFileC | Open a .docx file from disk into memory and return id. |
| docx-exportJsonC | Return the current JSON model for a given id. |
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 12 tools
Two tools (docx-open and docx-openFile) have identical descriptions, making them indistinguishable. This creates confusion for agents.
All tools follow a consistent docx-<verb><Noun> pattern with camelCase verbs. No naming convention violations.
12 tools cover the core DOCX operations reasonably well without being excessive or insufficient.
Basic CRUD is present but missing a delete/close operation for documents. Also lacks a way to create an empty document directly.