Doc Ops Mcp

Overview

What is Doc Ops MCP?

Doc Ops MCP is a universal server designed for document processing, conversion, and automation, supporting various formats like PDF, DOCX, HTML, and Markdown through a unified API.

How to use Doc Ops MCP?

To use Doc Ops MCP, integrate it into your MCP client by adding the server configuration and running the command npx -y doc-ops-mcp. You can also configure environment variables for output and cache directories.

Key features of Doc Ops MCP?

  • Supports multiple document formats for conversion and processing.
  • Provides content rewriting features including batch text replacement and format adjustments.
  • Allows adding watermarks and QR codes to PDF documents.
  • Smart conversion planning to optimize document processing.

Use cases of Doc Ops MCP?

  1. Converting documents between formats (e.g., DOCX to PDF).
  2. Enhancing PDF documents with watermarks and QR codes.
  3. Automating document content rewriting for consistency.
  4. Integrating with other tools for enhanced document processing capabilities.

FAQ from Doc Ops MCP?

  • What document formats are supported?

    Doc Ops MCP supports PDF, DOCX, HTML, and Markdown formats.

  • Is there a limit on file size?

    Yes, the maximum file size for processing is 50MB.

  • Can I run Doc Ops MCP in Docker?

    Yes, Doc Ops MCP can be deployed using Docker with pre-built images or by building from source.

Server Config

{
  "mcpServers": {
    "doc-ops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "doc-ops-mcp@latest"
      ],
      "env": {
        "OUTPUT_DIR": "/tmp/output",
        "CACHE_DIR": "/tmp/cache"
      }
    }
  }
}

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