Che Word Mcp
Automate creation and editing of Word .docx files from your agent with a Swift-native MCP server offering broad document tools.
Overview
io.github.kiki830621/che-word-mcp is a MCP server for the Build phase that exposes 105 Swift-native tools to create and edit Word .docx files for agents.
What is this MCP server?
- 105 MCP tools for Word .docx manipulation
- Swift-native implementation via mcpb CheWordMCP binary v1.8.0
- Stdio MCP transport for Claude Code, Cursor, and compatible clients
- Targets programmatic editing beyond copy-paste into Microsoft Word
- 105 MCP tools stated in registry description
- Version 1.8.0 CheWordMCP mcpb with published fileSha256
- Stdio transport per MCP server schema
Community signal: 5 GitHub stars.
What problem does it solve?
Agents that only output Markdown or plain text still force you to manually rebuild formatting when stakeholders require real .docx deliverables.
Who is it for?
Solo builders who must deliver Word documents and want agent-driven drafting, restructuring, and batch edits via MCP on a supported Mac setup.
Skip if: Teams standardized on Google Docs only, Linux-only workflows without the mcpb binary path, or users who need online co-editing instead of file-based docx.
What do I get? / Deliverables
After registration, your agent can apply structured .docx edits and document operations through 105 dedicated Word MCP tools.
- Agent-driven .docx creation and structured edits
- Access to 105 Word-oriented MCP tools
- Reduced manual round-trips between IDE and Microsoft Word
Recommended MCP Servers
Journey fit
Proposal, spec, and deliverable documents are produced while building; agents need first-class .docx manipulation in that docs subphase. docs is the canonical shelf for MCP servers that generate or refactor written artifacts developers still exchange as Word files.
How it compares
105-tool native .docx MCP server, not a Pandoc one-off script or a generic office macro skill.
Common Questions / FAQ
Who is che-word-mcp for?
Developers and indie builders who produce .docx specs and client docs and want MCP agents to manipulate Word files programmatically.
When should I use che-word-mcp?
Use it in build and docs when you are generating or refactoring Word deliverables from Claude Code or Cursor instead of manual Word sessions.
How do I add che-word-mcp to my agent?
Add the CheWordMCP v1.8.0 mcpb release to your stdio MCP configuration following the kiki830621/che-word-mcp GitHub setup, then invoke docx tools from the agent.