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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lihongjie0209/docx-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server