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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago