Word Document Tools

🚀 Word Tools MCP Server

A server implementing the Model Context Protocol (MCP) that provides AI-driven Word document operation capabilities. This server implements the MCP protocol, enabling AI applications to create, edit, and manage Word documents through natural language interaction.

✨ Features

• Complete implementation of the MCP protocol.
• Creation and management of Word documents.
• Manipulation of rich text content.
• Creation and formatting of tables.
• Control of document layout.
• Management of document metadata.
• Real-time monitoring of document status.

📦 Installation

Prerequisites

• Node.js version 14 or higher.
• Microsoft Word (optional, for advanced features).

Installation Commands

Install using npx:

npx @puchunjie/doc-tools-mcp

Or install globally:

npm install -g @puchunjie/doc-tools-mcp

Use as a project dependency:

npm install @puchunjie/doc-tools-mcp

💻 Usage Examples

Basic Usage

1. Start the MCP server:

npx @puchunjie/doc-tools-mcp

2. The server will start on port 8765 by default.
3. Configure your AI application (e.g., Cursor, VSCode) to use the MCP server:

http://localhost:8765

MCP Tools

The server provides the following MCP functions:

• create_document - Create a new Word document.

  • Parameters: filePath (required), title, author.

• open_document - Open an existing Word document.

  • Parameters: filePath (required).

• add_paragraph - Add a paragraph to the document.

  • Parameters: filePath (required), text (required), style, alignment.

• add_table - Add a table to the document.

  • Parameters: filePath (required), rows (required), cols (required), headers, data.

• search_and_replace - Find and replace text in the document.

  • Parameters: filePath (required), searchText (required), replaceText (required), matchCase.

• set_page_margins - Set the page margins of the document.

  • Parameters: filePath (required), top, right, bottom, left.

• get_document_info - Get the document metadata.

  • Parameters: filePath (required).

Integration with AI Applications

Cursor

1. Open the Cursor configuration file ~/.cursor/mcp.json.
2. Add the following configuration:

{
  "mcpServers": {
    "doc-tools-mcp": {
      "command": "npx",
      "args": [
        "@puchunjie/doc-tools-mcp"
      ]
    }
  }
}

Or for the local development version:

{
  "mcpServers": {
    "doc-tools-mcp": {
      "command": "node",
      "args": [
        "/path/to/your/doc-tools-mcp/dist/mcp-server.js"
      ]
    }
  }
}

After configuration, you can use natural language to operate Word documents:

"Create a new document named report.docx"
"Add the title 'Monthly Report' to report.docx"
"Insert a 4x3 table to contain sales data"

VSCode and Other MCP-Supported Applications

The integration steps with other MCP protocol-supported tools are similar. For specific configuration methods, please refer to here.

📚 Documentation

Development

• The project is written in Node.js and JavaScript, suitable for developers familiar with this technology stack.
• The core logic of the server is located in the server.js file, which is responsible for handling different MCP commands.
• Each functional module (e.g., document creation, paragraph addition) is implemented independently for easy maintenance and expansion.

Configuration

• The server listens on port 8765 by default. If you need to change the port, modify the corresponding configuration in server.js.
• It supports a custom plugin system, allowing developers to expand more functions. For specific methods, please refer to Expansion Document.

Example

Here is a simple usage example:

1. Install the server:

npm install @puchunjie/doc-tools-mcp

2. Start the server:

npx @puchunjie/doc-tools-mcp

3. Access http://localhost:8765 in your browser to view the provided API interfaces.

Issues and Support

If you encounter any problems, please visit the GitHub repository to view the documentation or submit an ISSUE. We have an active developer community to assist you.

📄 License

This project follows the MIT license. For specific details, please refer to the LICENSE file.