Docx/doc-MCP

Created By
MeterLonga year ago
A powerful Word document processing service based on FastMCP, enabling AI assistants to create, edit, and manage docx files with full formatting support. Preserves original styles when editing content.
Overview

What is MCP-Doc?

MCP-Doc is a powerful Word document processing service based on FastMCP, enabling AI assistants to create, edit, and manage docx files with full formatting support while preserving original styles.

How to use MCP-Doc?

To use MCP-Doc, install the required dependencies, set it up as an MCP service in Cursor, and then use natural language commands to operate on Word documents.

Key features of MCP-Doc?

  • Complete document operations including creating, opening, and saving documents.
  • Full formatting support for fonts, colors, sizes, and alignment.
  • Table processing capabilities for creating, editing, merging, and splitting cells.
  • Image insertion and layout control features.
  • Convenient editing functions like find and replace.

Use cases of MCP-Doc?

  1. Automating document creation and formatting tasks.
  2. Assisting users in editing Word documents through AI commands.
  3. Managing complex documents with tables and images efficiently.

FAQ from MCP-Doc?

  • Can MCP-Doc handle all types of Word documents?

Yes! MCP-Doc supports a wide range of Word document features and formatting options.

  • Is there a specific Python version required?

Yes! Python 3.10 or higher is required to run MCP-Doc.

  • How do I troubleshoot issues with MCP-Doc?

Ensure all dependencies are installed correctly and check the server path in Cursor.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MeterLong
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago