MCP server for creating, inspecting, editing, and validating Office Open XML documents (.docx, .pptx, .xlsx)
MCPpedia last refreshed this data
Ooxml MCP Server is an MCP server that MCP server for creating, inspecting, editing, and validating Office Open XML documents (.docx, .pptx, .xlsx). Its tool list has not been published yet over stdio and sse, requires no API key, and scores 39/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ooxml": {
"command": "ooxml-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for creating, inspecting, editing, and validating Office Open XML documents (.docx, .pptx, .xlsx) at the package/part level.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in writing
MCP server for document format conversion using pandoc.
This is an MCP server that allows you to directly download transcripts of YouTube videos.
Scrape, crawl, and map websites to Markdown or JSON via local CLI.
Any URL to clean, LLM-ready Markdown for RAG. Strips ads, nav, and boilerplate.
MCP Security Weekly
Get CVE alerts and security updates for Ooxml Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for creating, inspecting, editing, and validating Office Open XML documents (.docx, .pptx, .xlsx) at the package/part level.
Extracted from ai-ui as a standalone Model Context Protocol server.
| Tool | Description |
|---|---|
list_document_parts | List all internal ZIP parts (path, size, type) |
read_document_part | Read raw XML/content of a part |
create_document | Create a minimal valid docx/pptx/xlsx (optional custom parts) |
write_document_part | Write/replace one or more parts (atomic + validate) |
delete_document_part | Delete a part (only if result still validates) |
validate_document | Validate structure, relationships, content types, XLSX semantics |
All tools take filesystem paths (not application-specific file IDs). Writes are validated before saving; invalid packages are rejected and the original file is left unchanged.
go install github.com/Bajahaw/ooxml-mcp-server/cmd/ooxml-mcp@latest
Or build from source:
git clone https://github.com/Bajahaw/ooxml-mcp-server.git
cd ooxml-mcp-server
go build -o ooxml-mcp ./cmd/ooxml-mcp
Add to your MCP config (stdio):
{
"mcpServers": {
"ooxml": {
"command": "ooxml-mcp"
}
}
}
Or with an absolute path:
{
"mcpServers": {
"ooxml": {
"command": "/path/to/ooxml-mcp"
}
}
}
In ai-ui settings, add an MCP server pointing at the ooxml-mcp binary (or go run command) via stdio, or wrap it with an HTTP/SSE bridge if you use remote MCP.
Before any write is committed, the package is checked for:
.xml / .rels part[Content_Types].xml overrides and default extensionsr:id / r:embed / r:link references resolve1. create_document path=./report.docx format=docx
2. list_document_parts path=./report.docx
3. read_document_part path=./report.docx part_path=word/document.xml
4. write_document_part path=./report.docx parts={ "word/document.xml": "<w:document ...>..." }
5. validate_document path=./report.docx
MIT — see LICENSE.