Word Document Operations

io.github.swadegeiger1Published by GitHub account swadegeiger1v1.0.0Updated Oct 24, 2026

Read, create, and modify Microsoft Word documents

Overview

AI-generated overview

Lets an assistant read text from, create, and append content to Microsoft Word .docx files on the local machine.

What you can do
A minimal local MCP server built on python-docx that exposes three tools: read_word_document to extract text from a .docx file, create_word_document to make a new Word document, and append_to_document to add content to an existing one. It works with file paths on the user's machine and is intended for simple text-level document operations rather than complex formatting.
When to use it
Useful when an assistant needs to pull text out of Word documents or generate and extend .docx files as part of a local workflow, such as drafting memos or collecting notes into a document. It is a good fit for straightforward text content, not for advanced Word formatting or layout work.
Requirements
Runs as a local process on the user's machine (desktop only, not web-executable). Needs a Python 3 environment with the package installed from PyPI (word-mcp-server-swadegeiger1) and its dependencies, plus a local MCP client configuration pointing at the server script. No accounts, API keys, or environment variables are declared.
Before you install
The create and append tools write to files on the local disk, so an assistant can create or modify documents at paths it is given; review paths before allowing writes and keep backups of important files. No credentials or network access are declared.

Installation

In SourceWeft

  1. Open Word Document Operations in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.