Doc Ops Server

Created By
Tele-AI10 months ago
A Model Context Protocol server for seamless document format conversion and processing
Overview

What is Doc Ops Server?

Doc Ops Server is a Model Context Protocol server designed for seamless document format conversion and processing, supporting various formats like PDF, DOCX, HTML, and Markdown.

How to use Doc Ops Server?

To use Doc Ops Server, integrate it with your MCP client by adding the server configuration. You can then use commands to convert documents or apply enhancements like watermarks and QR codes.

Key features of Doc Ops Server?

  • Supports conversion between multiple document formats (PDF, DOCX, HTML, Markdown)
  • Document rewriting capabilities for content optimization
  • PDF enhancement features including watermark and QR code addition
  • Smart conversion planning for optimal processing

Use cases of Doc Ops Server?

  1. Converting DOCX files to PDF with automatic watermarking.
  2. Rewriting content in Markdown documents for better clarity.
  3. Batch processing of multiple documents for format conversion.

FAQ from Doc Ops Server?

  • Can Doc Ops Server handle large files?

Yes, it supports files up to 50MB in size.

  • Is there a limit on the number of concurrent conversions?

Yes, it supports up to 5 concurrent tasks.

  • What programming language is used for Doc Ops Server?

The server is implemented in pure JavaScript.

Server Config

{
  "mcpServers": {
    "doc-ops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "doc-ops-mcp@latest"
      ],
      "env": {
        "OUTPUT_DIR": "/tmp/output",
        "CACHE_DIR": "/tmp/cache"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Tele-AI
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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