doc-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_DIR | No | Directory for temporary and cache files | ~/.cache/doc-ops-mcp |
| OUTPUT_DIR | No | Controls where all generated files are saved | ~/Documents |
| QR_CODE_IMAGE | No | Default QR code image path for PDF files. Added to PDFs only when explicitly requested (addQrCode=true). Supported formats: PNG, JPG. If not set, QR code functionality will be unavailable | |
| WATERMARK_IMAGE | No | Default watermark image path for PDF files. Automatically added to all PDF conversions. Supported formats: PNG, JPG. If not set, default text watermark "doc-ops-mcp" will be used |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_documentC | Read various document formats (DOCX, DOC, TXT, MD, HTML, etc.) |
| write_documentC | Write content to document files in specified formats. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names based on content type (HTML, Markdown, or plain text). Supports intelligent format detection. |
| convert_documentA | Convert documents between formats with enhanced style preservation. Output directory is controlled by OUTPUT_DIR environment variable. All output files will be automatically saved to the directory specified by OUTPUT_DIR with auto-generated names. ⚠️ IMPORTANT: For Markdown to HTML conversion with style preservation, use 'convert_markdown_to_html' tool instead for better results with themes and styling. For creating Word documents from content, use 'create_word_document' tool to avoid conversion loops. |
| add_watermarkA | Add watermarks to PDF documents. Supports both text and image watermarks. Priority: user text > user image > environment variable image > default text "doc-ops-mcp" |
| add_qrcodeB | Add QR code to PDF documents with friendly text below. QR code must be an image file (PNG/JPG). Priority: user provided path > environment variable QR_CODE_IMAGE |
| convert_docx_to_pdfB | Enhanced DOCX to PDF conversion with perfect Word style replication and Playwright integration. Watermark can be added by setting addWatermark=true (uses WATERMARK_IMAGE environment variable or default text "doc-ops-mcp"). QR code can be added by setting addQrCode=true (requires QR_CODE_IMAGE environment variable). Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. |
| convert_markdown_to_htmlA | Enhanced Markdown to HTML conversion with beautiful styling and theme support. Supports GitHub, Academic, Modern, and Default themes with complete style preservation. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. |
| convert_markdown_to_docxA | Enhanced Markdown to DOCX conversion with professional styling and theme support. Preserves formatting, supports tables, lists, headings, and inline formatting with beautiful Word document output. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. |
| convert_markdown_to_pdfA | Enhanced Markdown to PDF conversion with beautiful styling and theme support. Watermark can be added by setting addWatermark=true (uses WATERMARK_IMAGE environment variable or default text "doc-ops-mcp"). QR code can be added by setting addQrCode=true (requires QR_CODE_IMAGE environment variable). Requires playwright-mcp for final PDF generation. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. |
| convert_html_to_markdownB | Enhanced HTML to Markdown conversion with style preservation. Converts HTML files to clean Markdown format while preserving structure, links, images, tables, and formatting. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. |
| create_word_documentB | Create a Word document directly from content with beautiful formatting. This tool is specifically designed for creating Word documents from scratch, avoiding conversion loops. Supports HTML content with automatic styling and formatting. Output directory is controlled by OUTPUT_DIR environment variable. Files will be automatically saved to OUTPUT_DIR with auto-generated names. |
| plan_conversionA | 🎯 MANDATORY FIRST STEP - Smart Document Conversion Planner - ⚠️ CRITICAL: This tool MUST be executed BEFORE any document conversion operation! When users request any format conversion (e.g., 'convert MD to PDF', 'DOCX to HTML'), you MUST call this tool first to get the optimal conversion plan, then follow the plan's steps exactly. This ensures proper conversion workflow and handles complex multi-step conversions. For PDF conversions, note that playwright-mcp integration is required for final PDF generation, followed by process_pdf_post_conversion for watermarks/QR codes. Supports all format conversion path planning. |
| process_pdf_post_conversionA | 🔧 PDF Post-Processing Unified Tool - ⚠️ IMPORTANT: This is a necessary follow-up step for playwright-mcp's browser_pdf_save command! After using playwright-mcp to generate PDF, this tool must be called immediately to complete final processing. Features include: 1) Automatically move PDF from playwright temporary path to target location 2) Uniformly add watermarks and QR codes 3) Clean up temporary files. Workflow: playwright-mcp:browser_pdf_save → doc-ops-mcp:process_pdf_post_conversion |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
The tool set has clear functional distinctions between major categories (conversion, enhancement, planning, reading/writing), but there is significant overlap and confusion within conversion tools. For example, 'convert_document' is a general tool that overlaps with specific converters like 'convert_markdown_to_html', and the descriptions explicitly warn against using it for certain tasks, creating ambiguity about when to choose which tool. The planning and post-processing tools have distinct purposes but add complexity to the workflow.
Most tools follow a consistent verb_noun pattern (e.g., 'add_qrcode', 'convert_document', 'read_document'), which is clear and predictable. However, there are minor deviations: 'plan_conversion' uses a noun_verb structure, and 'process_pdf_post_conversion' is a longer, less standard name. Overall, the naming is mostly consistent and readable, with only a few outliers.
With 13 tools, the count is reasonable for a document operations server covering conversion, enhancement, and management tasks. It's slightly on the higher side but justified by the domain complexity. However, some tools like 'plan_conversion' and 'process_pdf_post_conversion' add procedural steps that might inflate the count unnecessarily, making it borderline heavy but still appropriate.
The tool surface covers a wide range of document operations, including reading, writing, converting between multiple formats, adding watermarks/QR codes, and planning workflows. There are no obvious major gaps for core document handling. However, the reliance on external tools like 'playwright-mcp' for PDF generation and the need for mandatory planning steps introduce dependencies that could limit standalone completeness, though the server itself provides good coverage.