MCP Office Word

io.github.dosev-aiPublished by GitHub account dosev-aiv0.7.0Updated Oct 24, 2026

50-tool Word MCP server. Document assembly, tracked changes, and export. Windows-first.

VerifiedSTDIODesktop onlyProductivity & Workflow Files & Storage

Server details

Identifier: io.github.dosev-ai/mcp-office-word
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account dosev-ai for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.dosev-ai%2Fmcp-office-word.svg)](https://sourceweft.com/mcp/io.github.dosev-ai%2Fmcp-office-word?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local Windows MCP server that gives an assistant 50 tools to assemble, edit, review and export Microsoft Word documents.

What you can do: Read and inspect Word documents within allowed directories, including structural checks and QA of document layout and content. Assemble documents from templates and edit content and styles when write mode is enabled. Manage tracked changes and export documents to PDF or HTML through Word COM automation. Report the server's available capabilities and tool list.
When to use it: Useful when you work with .docx files on Windows and want an assistant to build documents from templates, apply edits and styles, review tracked changes, or export to PDF or HTML, while keeping file access limited to chosen folders.
Requirements: Runs locally as a Python process (Python 3.11 or later) on Windows 10 or 11, installed from the mcp-office package and started via stdio. WORD_ALLOWLIST_ROOTS is required to grant file access. Microsoft Word is needed for COM-backed tools such as tracked changes and PDF/HTML export; read-only docx tools work without it. An MCP client such as Claude Desktop or VS Code Copilot is needed.

Before you install

Write operations and COM tools are off unless WORD_ENABLE_WRITE or WORD_ENABLE_COM is set to true; enabling them lets the assistant modify document content and styles. File access is confined to the directories listed in WORD_ALLOWLIST_ROOTS, so keep that list narrow. The README warns that a similarly named package on PyPI is unrelated third-party code; install only the mcp-office package.

Installation

In SourceWeft

Open MCP Office Word in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP Office

Local-first, governed MCP servers for Microsoft Office — built for developers who want to treat Office files the way they treat code.

[License: MIT] [Python 3.11+] [CI] [PyPI] [UAT]

What is this?

MCP Office is a suite of Model Context Protocol servers that expose Microsoft Office capabilities as governed, deterministic tool calls. Each server runs locally on Windows, connects to your MCP client (Claude Desktop, VS Code Copilot, or any MCP-compatible client), and gives you structured control over Office files — without an in-app AI assistant.

This is not a Copilot replacement. It is a developer-first execution layer for Office automation.

Packages

✅ Available now

Package	What it does	Install	Tools
`excelmcp`	Read, write, style, validate, and export Excel workbooks	`pip install mcp-office`	65
`pptmcp`	Build, edit, review, and export PowerPoint presentations. Output Contract framework for machine-verifiable slide specs	`pip install mcp-office`	51
`wordmcp`	Template assembly, tracked-changes support, and structural QA for Word documents	`pip install mcp-office`	50

🚧 Coming next

MailMCP is now included in the repository's single mcp-office source distribution, but the currently published PyPI artifact does not yet claim MailMCP availability. See mailmcp/README.md for source validation while Windows Outlook UAT and release verification remain open.

New packages are added as they complete their proof cycle. See ROADMAP.md.

Quick start

Prerequisites

Windows 10 or 11
Python 3.11 or later (python --version)
Claude Desktop or VS Code with GitHub Copilot
Microsoft Office (Excel / PowerPoint / Word) — required for COM-backed tools (styling, PDF export, tracked-changes)
Classic Microsoft Outlook desktop — required for MailMCP

Install

PyPI note: excelmcp on PyPI is an unrelated third-party package. Do not pip install excelmcp — that ships you a stranger's code. The published suite package is mcp-office.

Or clone and install the consolidated suite from source (including MailMCP and Windows COM support):

bash

git clone https://github.com/dosev-ai/mcp-office.gitcd mcp-officepython -m venv .venv.venv\Scripts\activatepython -m pip install -e ".[com]"

git clone https://github.com/dosev-ai/mcp-office.gitcd mcp-officepython -m venv .venv.venv\Scripts\activatepython -m pip install -e ".[com]"

Configure Claude Desktop

Open %APPDATA%\Claude\claude_desktop_config.json (create it if it doesn't exist) and add the servers you installed:

json

{  "mcpServers": {    "excel-excelmcp": {      "command": "python",      "args": ["-m", "excelmcp.server"],      "env": {        "EXCEL_ALLOWLIST_ROOTS": "C:\\path\\to\\your\\files",        "EXCEL_ENABLE_WRITE": "true"      }    },    "powerpoint-pptmcp": {      "command": "python",      "args": ["-m", "pptmcp.server"],      "env": {        "PPT_ALLOWLIST_ROOTS": "C:\\path\\to\\your\\files",        "PPT_ENABLE_WRITE": "true"      }    },    "word-wordmcp": {      "command": "python",      "args": ["-m", "wordmcp.server"],      "env": {        "WORD_ALLOWLIST_ROOTS": "C:\\path\\to\\your\\files",        "WORD_ENABLE_WRITE": "true"      }    }  }}

{  "mcpServers": {    "excel-excelmcp": {      "command": "python",      "args": ["-m", "excelmcp.server"],      "env": {        "EXCEL_ALLOWLIST_ROOTS": "C:\\path\\to\\your\\files",        "EXCEL_ENABLE_WRITE": "true"      }    },    "powerpoint-pptmcp": {      "command": "python",      "args": ["-m", "pptmcp.server"],      "env": {        "PPT_ALLOWLIST_ROOTS": "C:\\path\\to\\your\\files",        "PPT_ENABLE_WRITE": "true"      }    },    "word-wordmcp": {      "command": "python",      "args": ["-m", "wordmcp.server"],      "env": {        "WORD_ALLOWLIST_ROOTS": "C:\\path\\to\\your\\files",        "WORD_ENABLE_WRITE": "true"      }    }  }}

Replace C:\\path\\to\\your\\files with the directory where your Office files live. Restart Claude Desktop after saving.

Verify

In Claude Desktop, send:

Call capabilities() on excel-excelmcpCall capabilities() on powerpoint-pptmcpCall capabilities() on word-wordmcp

Call capabilities() on excel-excelmcpCall capabilities() on powerpoint-pptmcpCall capabilities() on word-wordmcp

Each should return a tool list (65 for Excel, 51 for PowerPoint, 50 for Word). If a server is missing, check that python resolves to the venv where you installed mcp-office.

Full per-package guides: excelmcp/README.md · pptmcp/README.md · wordmcp/README.md · mailmcp/README.md (source-integrated; release pending)

Detailed step-by-step: docs/quickstart.md

Requirements

Requirement	Notes
Windows 10 or 11	COM automation requires Windows
Python 3.11+	`python --version` to confirm
Microsoft Office	Required for COM-dependent tools (styling, PDF export, tracked-changes). Read-only docx/xlsx/pptx tools work without Office.
Classic Outlook desktop	Required for MailMCP. MailMCP remains release-pending until Windows Outlook UAT and published-artifact verification pass.
MCP client	Claude Desktop or VS Code with Copilot

Architecture

Your MCP client (Claude Desktop / VS Code Copilot / other)        │        │  MCP stdio protocol        ↓  MCP Office servers (local Python processes)   ├─ excelmcp    — Excel automation (live)   ├─ pptmcp      — PowerPoint automation (live)   ├─ wordmcp     — Word automation (live)   └─ mailmcp     — Outlook automation (source-integrated; release pending)        │        │  COM / Outlook COM / openpyxl / python-pptx / python-docx        ↓  Microsoft Office (local installation)

Your MCP client (Claude Desktop / VS Code Copilot / other)        │        │  MCP stdio protocol        ↓  MCP Office servers (local Python processes)   ├─ excelmcp    — Excel automation (live)   ├─ pptmcp      — PowerPoint automation (live)   ├─ wordmcp     — Word automation (live)   └─ mailmcp     — Outlook automation (source-integrated; release pending)        │        │  COM / Outlook COM / openpyxl / python-pptx / python-docx        ↓  Microsoft Office (local installation)

Each server is a standalone local stdio MCP process. MCP Office does not add a hosted service; Microsoft Office and your MCP client/model may still have their own sync and data-handling boundaries.

Contributing

This project is in active development. The best way to contribute right now:

Try any package (excelmcp, pptmcp, wordmcp) and open a First Run Report
Report bugs via GitHub Issues
Ask questions or share what you built in GitHub Discussions

See CONTRIBUTING.md for development guidelines.

License

MIT — see LICENSE.

Source: README.md at commit d8f84dd

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.7.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts