Give your AI coding agent the ability to create, read, and edit Word documents. Edits appear as tracked changes in Microsoft Word — red strikethrough
Connect Docx MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Give your AI coding agent the ability to create, read, and edit Word documents. Edits appear as tracked changes in Microsoft Word — red strikethrough for deletions, green underline for insertions — and after any revision session your agent. The docx mcp mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Legal — contract review with tracked redlines, batch clause replacement across templates, comment annotations explaining each change, footnote managementConsulting — build proposals and SOWs from templates, convert meeting notes to formatted deliverables, bulk-update payment terms across document setsdocx-mcp — serverproposal_v1_diff.docx — open in Word to see tracked changes inlineproposal_v1_diff.txt — plain-text summary, ready to paste anywhereSingle — token names with no surrounding contextNon — English names (Arabic, CJK, African name patterns have low recall on this English model)Capability — What your agent can doComments — Add comments anchored to specific paragraphs, reply to comment threadsTables — Create tables, modify cells, add or delete rows — all with revision trackingFormatting — Bold, italic, underline, color — with revision tracking so formatting changes are visibleImages — List embedded images, insert new ones with specified dimensionsdocx-mcp-server on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Docx MCP's toolset — Legal, Consulting, docx-mcp and 11 more — is a fair guide to whether it matches your workflow. It is maintained by securityronin; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Legal | contract review with tracked redlines, batch clause replacement across templates, comment annotations explaining each change, footnote management |
| Consulting | build proposals and SOWs from templates, convert meeting notes to formatted deliverables, bulk-update payment terms across document sets |
| docx-mcp | server |
| proposal_v1_diff.docx | open in Word to see tracked changes inline |
| proposal_v1_diff.txt | plain-text summary, ready to paste anywhere |
| Single | token names with no surrounding context |
| Non | English names (Arabic, CJK, African name patterns have low recall on this English model) |
| Capability | What your agent can do |
| Comments | Add comments anchored to specific paragraphs, reply to comment threads |
| Tables | Create tables, modify cells, add or delete rows — all with revision tracking |
| Formatting | Bold, italic, underline, color — with revision tracking so formatting changes are visible |
| Images | List embedded images, insert new ones with specified dimensions |
| Cross-references | Internal hyperlinks between paragraphs with bookmarks |
| Protection | Lock documents for tracked-changes-only, read-only, or comments-only with passwords |
{
"mcpServers": {
"docx": {
"command": "uvx",
"args": ["docx-mcp-server"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.